Skip to content

Commit 1cf2f6f

Browse files
author
RiniAngreani
committed
Update AppSchemaDataAccess.xsd in tutorial.
1 parent 26f52e4 commit 1cf2f6f

File tree

3 files changed

+96
-45
lines changed

3 files changed

+96
-45
lines changed

data/app-schema-tutorial/workspaces/gsml/gsml_GeologicUnit/AppSchemaDataAccess.xsd

+32-15
Original file line numberDiff line numberDiff line change
@@ -237,23 +237,16 @@
237237
Flag to indicate that we want to connect to an xml data source]]>
238238
</documentation>
239239
</annotation>
240-
</element>
241-
<element name="groupBy" minOccurs="0" maxOccurs="1">
240+
</element>
241+
<element name="isDenormalised" type="boolean" default="true" minOccurs="0">
242242
<annotation>
243243
<documentation>
244244
<![CDATA[
245-
This is how we achieve our basic support for multivalued properties. If you have a source featuretype
246-
serving features produced by a join query, you have to specify here as many GroupByAttribute
247-
elements as attributes needed to make a unique feature from the joined results, so complex datastore
248-
will be able of recognizing where a target feature with multiple valued attributes ends.
249-
]]>
245+
Flag to indicate if the data is denormalised or not. If data is not denormalised
246+
(flag = false) then its safe for us to apply the system configured maxFeatures
247+
value when building the SQL query to run ]]>
250248
</documentation>
251249
</annotation>
252-
<complexType>
253-
<sequence>
254-
<element name="GroupByAttribute" type="string" minOccurs="0" maxOccurs="unbounded" />
255-
</sequence>
256-
</complexType>
257250
</element>
258251
<element name="attributeMappings" minOccurs="0">
259252
<annotation>
@@ -327,7 +320,16 @@
327320
</annotation>
328321
<sequence>
329322
<choice minOccurs="0">
330-
<element name="OCQL" type="string" />
323+
<sequence>
324+
<element name="OCQL" type="string" />
325+
<element name="index" type="string" minOccurs="0" maxOccurs="1">
326+
<annotation>
327+
<documentation>
328+
<![CDATA[ The index of database row if denormalised. Example of usage is timeseries endPosition that reflects the last timePosition where the timePosition value is dynamic. ]]>
329+
</documentation>
330+
</annotation>
331+
</element>
332+
</sequence>
331333
<element name="Expression">
332334
<complexType>
333335
<sequence>
@@ -443,8 +445,23 @@
443445
<![CDATA[ Flag to indicate the target element addressed by this mapping has to be treated as
444446
a multivalued property. AppSchemaDataAccess will treat all the attribute mappings having this flag
445447
set to true as multivalued attributes and will create as many instances of it as Features of
446-
the surrogate datastore lie inside the group mapping, as defined by the groupBy element in
447-
a FeatureTypeMapping ]]>
448+
the surrogate datastore lie inside the FeatureTypeMapping ]]>
449+
</documentation>
450+
</annotation>
451+
</element>
452+
<element name="encodeIfEmpty" type="boolean" default="false" minOccurs="0">
453+
<annotation>
454+
<documentation>
455+
<![CDATA[ Flag to determine whether to skip a attribute mapping if it is empty default to false]]>
456+
</documentation>
457+
</annotation>
458+
</element>
459+
<element name="isList" type="boolean" default="false" minOccurs="0">
460+
<annotation>
461+
<documentation>
462+
<![CDATA[ Flag to indicate the target element addressed by this mapping has to be treated as
463+
a container of a list of values. This is similar to isMultiple except the values are concatenated
464+
as one big value instead of multiple elements with each value.]]>
448465
</documentation>
449466
</annotation>
450467
</element>

data/app-schema-tutorial/workspaces/gsml/gsml_MappedFeature/AppSchemaDataAccess.xsd

+32-15
Original file line numberDiff line numberDiff line change
@@ -237,23 +237,16 @@
237237
Flag to indicate that we want to connect to an xml data source]]>
238238
</documentation>
239239
</annotation>
240-
</element>
241-
<element name="groupBy" minOccurs="0" maxOccurs="1">
240+
</element>
241+
<element name="isDenormalised" type="boolean" default="true" minOccurs="0">
242242
<annotation>
243243
<documentation>
244244
<![CDATA[
245-
This is how we achieve our basic support for multivalued properties. If you have a source featuretype
246-
serving features produced by a join query, you have to specify here as many GroupByAttribute
247-
elements as attributes needed to make a unique feature from the joined results, so complex datastore
248-
will be able of recognizing where a target feature with multiple valued attributes ends.
249-
]]>
245+
Flag to indicate if the data is denormalised or not. If data is not denormalised
246+
(flag = false) then its safe for us to apply the system configured maxFeatures
247+
value when building the SQL query to run ]]>
250248
</documentation>
251249
</annotation>
252-
<complexType>
253-
<sequence>
254-
<element name="GroupByAttribute" type="string" minOccurs="0" maxOccurs="unbounded" />
255-
</sequence>
256-
</complexType>
257250
</element>
258251
<element name="attributeMappings" minOccurs="0">
259252
<annotation>
@@ -327,7 +320,16 @@
327320
</annotation>
328321
<sequence>
329322
<choice minOccurs="0">
330-
<element name="OCQL" type="string" />
323+
<sequence>
324+
<element name="OCQL" type="string" />
325+
<element name="index" type="string" minOccurs="0" maxOccurs="1">
326+
<annotation>
327+
<documentation>
328+
<![CDATA[ The index of database row if denormalised. Example of usage is timeseries endPosition that reflects the last timePosition where the timePosition value is dynamic. ]]>
329+
</documentation>
330+
</annotation>
331+
</element>
332+
</sequence>
331333
<element name="Expression">
332334
<complexType>
333335
<sequence>
@@ -443,8 +445,23 @@
443445
<![CDATA[ Flag to indicate the target element addressed by this mapping has to be treated as
444446
a multivalued property. AppSchemaDataAccess will treat all the attribute mappings having this flag
445447
set to true as multivalued attributes and will create as many instances of it as Features of
446-
the surrogate datastore lie inside the group mapping, as defined by the groupBy element in
447-
a FeatureTypeMapping ]]>
448+
the surrogate datastore lie inside the FeatureTypeMapping ]]>
449+
</documentation>
450+
</annotation>
451+
</element>
452+
<element name="encodeIfEmpty" type="boolean" default="false" minOccurs="0">
453+
<annotation>
454+
<documentation>
455+
<![CDATA[ Flag to determine whether to skip a attribute mapping if it is empty default to false]]>
456+
</documentation>
457+
</annotation>
458+
</element>
459+
<element name="isList" type="boolean" default="false" minOccurs="0">
460+
<annotation>
461+
<documentation>
462+
<![CDATA[ Flag to indicate the target element addressed by this mapping has to be treated as
463+
a container of a list of values. This is similar to isMultiple except the values are concatenated
464+
as one big value instead of multiple elements with each value.]]>
448465
</documentation>
449466
</annotation>
450467
</element>

data/app-schema-tutorial/workspaces/tut/tut_RoadSegment/AppSchemaDataAccess.xsd

+32-15
Original file line numberDiff line numberDiff line change
@@ -237,23 +237,16 @@
237237
Flag to indicate that we want to connect to an xml data source]]>
238238
</documentation>
239239
</annotation>
240-
</element>
241-
<element name="groupBy" minOccurs="0" maxOccurs="1">
240+
</element>
241+
<element name="isDenormalised" type="boolean" default="true" minOccurs="0">
242242
<annotation>
243243
<documentation>
244244
<![CDATA[
245-
This is how we achieve our basic support for multivalued properties. If you have a source featuretype
246-
serving features produced by a join query, you have to specify here as many GroupByAttribute
247-
elements as attributes needed to make a unique feature from the joined results, so complex datastore
248-
will be able of recognizing where a target feature with multiple valued attributes ends.
249-
]]>
245+
Flag to indicate if the data is denormalised or not. If data is not denormalised
246+
(flag = false) then its safe for us to apply the system configured maxFeatures
247+
value when building the SQL query to run ]]>
250248
</documentation>
251249
</annotation>
252-
<complexType>
253-
<sequence>
254-
<element name="GroupByAttribute" type="string" minOccurs="0" maxOccurs="unbounded" />
255-
</sequence>
256-
</complexType>
257250
</element>
258251
<element name="attributeMappings" minOccurs="0">
259252
<annotation>
@@ -327,7 +320,16 @@
327320
</annotation>
328321
<sequence>
329322
<choice minOccurs="0">
330-
<element name="OCQL" type="string" />
323+
<sequence>
324+
<element name="OCQL" type="string" />
325+
<element name="index" type="string" minOccurs="0" maxOccurs="1">
326+
<annotation>
327+
<documentation>
328+
<![CDATA[ The index of database row if denormalised. Example of usage is timeseries endPosition that reflects the last timePosition where the timePosition value is dynamic. ]]>
329+
</documentation>
330+
</annotation>
331+
</element>
332+
</sequence>
331333
<element name="Expression">
332334
<complexType>
333335
<sequence>
@@ -443,8 +445,23 @@
443445
<![CDATA[ Flag to indicate the target element addressed by this mapping has to be treated as
444446
a multivalued property. AppSchemaDataAccess will treat all the attribute mappings having this flag
445447
set to true as multivalued attributes and will create as many instances of it as Features of
446-
the surrogate datastore lie inside the group mapping, as defined by the groupBy element in
447-
a FeatureTypeMapping ]]>
448+
the surrogate datastore lie inside the FeatureTypeMapping ]]>
449+
</documentation>
450+
</annotation>
451+
</element>
452+
<element name="encodeIfEmpty" type="boolean" default="false" minOccurs="0">
453+
<annotation>
454+
<documentation>
455+
<![CDATA[ Flag to determine whether to skip a attribute mapping if it is empty default to false]]>
456+
</documentation>
457+
</annotation>
458+
</element>
459+
<element name="isList" type="boolean" default="false" minOccurs="0">
460+
<annotation>
461+
<documentation>
462+
<![CDATA[ Flag to indicate the target element addressed by this mapping has to be treated as
463+
a container of a list of values. This is similar to isMultiple except the values are concatenated
464+
as one big value instead of multiple elements with each value.]]>
448465
</documentation>
449466
</annotation>
450467
</element>

0 commit comments

Comments
 (0)