Skip to content

Commit

Permalink
0000043: Expressions for target_schema_name
Browse files Browse the repository at this point in the history
  • Loading branch information
erilong committed Dec 26, 2014
1 parent 503a394 commit 4f871fc
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 8 deletions.
14 changes: 8 additions & 6 deletions symmetric-assemble/src/asciidoc/configuration/routers.ad
Original file line number Diff line number Diff line change
Expand Up @@ -47,12 +47,14 @@ Router Expression:: An expression that is specific to the type of router that is
Sync on Update:: Flag that indicates that this router should route updates.
Sync on Insert:: Flag that indicates that this router should route inserts.
Sync on Delete:: Flag that indicates that this router should route deletes.
Target Catalog:: Optional name for the catalog a target table is in. Only use this if the target table is not in the default catalog.
If this field is left blank, then the source_catalog_name for the trigger will be used as the target name.
If the target name should be left blank and the source name is set, then the token of $(none) may be used to force the target name to be blanked out.
Target Schema:: Optional name of the schema a target table is in. On use this if the target table is not in the default schema.
If this field is left blank, then the source_schema_name for the trigger will be used as the target name.
If the target name should be left blank and the source name is set, then the token of $(none) may be used to force the target name to be blanked out.
Target Catalog:: Optional name of catalog where a target table is located.
If this field is unspecified, the catalog will be either the default catalog at the target node or the "source catalog name" from the table trigger,
depending on how "use source catalog schema" is set for the router. Variables are substituted for $(sourceNodeId), $(sourceExternalId), $(sourceNodeGroupId),
$(targetNodeId), $(targetExternalId), $(targetNodeGroupId), and $(none).
Target Schema:: Optional name of schema where a target table is located.
If this field is unspecified, the schema will be either the default schema at the target node or the "source schema name" from the table trigger,
depending on how "use source catalog schema" is set for the router. Variables are substituted for $(sourceNodeId), $(sourceExternalId), $(sourceNodeGroupId),
$(targetNodeId), $(targetExternalId), $(targetNodeGroupId), and $(none).
Use Source Catalog/Schema:: Whether or not to assume that the target catalog/schema name should be the same as the source catalog/schema name. The target catalog or schema name will still override if not blank.
Target Table:: Optional name for a target table. Only use this if the target table name is different than the source.

Expand Down
4 changes: 2 additions & 2 deletions symmetric-core/src/main/resources/symmetric-schema.xml
Original file line number Diff line number Diff line change
Expand Up @@ -594,8 +594,8 @@

<table name="router" description="Configure a type of router from one node group to another. Note that routers are mapped to triggers through trigger_routers.">
<column name="router_id" type="VARCHAR" size="50" required="true" primaryKey="true" description="Unique description of a specific router" />
<column name="target_catalog_name" type="VARCHAR" size="255" description="Optional name for the catalog a target table is in. Only use this if the target table is not in the default catalog. If this field is left blank, then the source_catalog_name for the trigger will be used as the target name. If the target name should be left blank and the source name is set, then the token of $(none) may be used to force the target name to be blanked out." />
<column name="target_schema_name" type="VARCHAR" size="255" description="Optional name of the schema a target table is in. On use this if the target table is not in the default schema. If this field is left blank, then the source_schema_name for the trigger will be used as the target name. If the target name should be left blank and the source name is set, then the token of $(none) may be used to force the target name to be blanked out." />
<column name="target_catalog_name" type="VARCHAR" size="255" description="Optional name of catalog where a target table is located. If this field is unspecified, the catalog will be either the default catalog at the target node or the source_catalog_name from the trigger, depending on how use_source_catalog_schema is set on the router. Variables are substituted for $(sourceNodeId), $(sourceExternalId), $(sourceNodeGroupId), $(targetNodeId), $(targetExternalId), $(targetNodeGroupId), and $(none)." />
<column name="target_schema_name" type="VARCHAR" size="255" description="Optional name of schema where a target table is located. If this field is unspecified, the schema will be either the default schema at the target node or the source_schema_name from the trigger, depending on how use_source_catalog_schema is set on the router. Variables are substituted for $(sourceNodeId), $(sourceExternalId), $(sourceNodeGroupId), $(targetNodeId), $(targetExternalId), $(targetNodeGroupId), and $(none)." />
<column name="target_table_name" type="VARCHAR" size="255" description="Optional name for a target table. Only use this if the target table name is different than the source." />
<column name="source_node_group_id" type="VARCHAR" size="50" required="true" description="Routers with this node_group_id will install triggers that are mapped to this router." />
<column name="target_node_group_id" type="VARCHAR" size="50" required="true" description="The node_group_id for nodes to route data to. Note that routing can be further narrowed down by the configured router_type and router_expression." />
Expand Down

0 comments on commit 4f871fc

Please sign in to comment.