User Tools

Site Tools


excluding_columns

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
excluding_columns [2015/12/15 11:02]
mark.english
excluding_columns [2017/09/21 16:12] (current)
jackson.davenport cleanup
Line 3: Line 3:
 The Replicator Agent supports excluding columns from replication. Please note that the preferred approach for excluding columns from being replicated is to leverage capabilities of the producer such as Perspectium Views which provides the ability to define which columns should be replicated. The Replicator Agent supports excluding columns from replication. Please note that the preferred approach for excluding columns from being replicated is to leverage capabilities of the producer such as Perspectium Views which provides the ability to define which columns should be replicated.
  
-Configuring columns to be excluded should be done prior to the Agent creating the table which contains the excluded column for clarity. ​Since multiple columns ​can be configured for exclusion all columns that are to be excluded are contained within the <​exclude_columns>​ directiveEach column ​to be excluded is defined within the <​exclude_columns>​ directive using a single <​exclude_column>​ entry for each column to be excluded. The <​exclude_columns>​ and enclosed <​exclude_column>​ entries must be placed within the <​subscribe>​ element located within the agent.xml configuration fileConsider the following:+Configuring columns to be excluded should be done prior to the Agent creating the table which contains the excluded column for clarity. ​However, it can be done after with no ill affectThat column ​will just no longer ​be populated
  
-   <​subscribe>​ +You can configure multiple columns to be excluded. To set this up you will have one <​exclude_columns>​...</​exclude_columns>​ set of tags. Within in it you will define each column to be excluded by individual <​exclude_column>​...</​exclude_column>​ tags. This will be placed within the <​subscribe>​ element located within the agent.xml configuration file.  Example below: 
-         ​<​exclude_columns>​+ 
 +<code XML> 
 +<?xml version="​1.0"​ encoding="​ISO-8859-1"​ standalone="​no"?>​ 
 +<​config>​ 
 +    <​agent>​ 
 +        ​<​subscribe>​ 
 +         <​task>​ 
 +                <​task_name>​example_subscribe</​task_name>​ 
 +                <​message_connection>​amqps://​example.perspectium.net</​message_connection>​ 
 +                . 
 +                . 
 +                . 
 +            </​task>​ 
 +              
 +            ​<​exclude_columns
 +                <​exclude_column>​sys_translated_text</​exclude_column>
                 <​exclude_column>​fx_price</​exclude_column>​                 <​exclude_column>​fx_price</​exclude_column>​
                 <​exclude_column>​sys_tags</​exclude_column>​                 <​exclude_column>​sys_tags</​exclude_column>​
-        ​</​exclude_columns>​ +            ​</​exclude_columns>​ 
-         + 
-        ​Other configuration directives... +        ​</​subscribe>​ 
-         +            ​ 
-    </subscribe/>+        ​<​max_reads_per_connect>​4000</​max_reads_per_connect>​ 
 +        ​<​polling_interval>​5</​polling_interval>​ 
 +    </agent> 
 +</config>
  
-In the example above we've added the necessary configuration to exclude the fx_price ​and sys_tags ​columns. ​Currently, when a column is excluded it's applied to every table which may contain the column.+</​code>​ 
 +  
 +In the example above we've added the necessary configuration to exclude the columns:  
 +  * fx_price 
 +  * sys_tags 
 +  * sys_translated_text 
 +Currently, when a column is excluded it's applied to every table which may contain the column.
  
excluding_columns.txt · Last modified: 2017/09/21 16:12 by jackson.davenport