-
Notifications
You must be signed in to change notification settings - Fork 246
/
all-config.xml
81 lines (66 loc) · 2.96 KB
/
all-config.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
<?xml version="1.0" encoding="UTF-8" standalone="no"?><?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<configuration>
<!-- The settings provided by this file will be in effect for ALL registered datatypes during ingest -->
<property>
<name>all.use.default.type.handlers</name>
<value>true</value>
<description>Flag to indicate that we've supplied configuration for the special "ALL" type, which
tells the event mapper to apply 'all.handler.classes' to each registered datatype</description>
</property>
<property>
<name>all.handler.classes</name>
<value>${ALL_HANDLER_CLASSES}</value>
<description>Datatype handlers to be utilized by all registered datatypes (in *addition* to any distinct handlers
that they may have set independently via their respective *-config.xml files)</description>
</property>
<property>
<name>all.ingest.helper.class</name>
<value></value>
</property>
<property>
<name>all.reader.class</name>
<value></value>
</property>
<property>
<name>all.data.category.marking.upstream.error</name>
<value>SOMEDOMAIN=SOMEMARKING</value>
<description>If any record comes into the system with this security marking, then recognize it as an upstream error
which is considered to be FATAL in this system</description>
</property>
<property>
<description>Properties to include in the accumulo table config cache</description>
<name>cache.table.properties</name>
<value>table.file.compress.*,table.file.blocksize,table.file.replication,table.iterator.minc.*,crypto.*</value>
</property>
<property>
<name>all.filter.classes</name>
<value>${ALL_FILTER_CLASSES}</value>
<description>This is the chain of context writers that will receive the output of all handlers and
higher prioriy content writers</description>
</property>
<property>
<name>all.filter.priority</name>
<value>50</value>
<description> This is the priority of this context writer chain</description>
</property>
<property>
<name>all.data.combine.separator</name>
<value>:</value>
<description>Output separator for Virtual Fields</description>
</property>
<!-- Set up the default policy enforcer class here, this will be used system wide -->
<!-- Additional enforcers can be enabled for specific data types in their respective config files-->
<property>
<name>all.ingest.policy.enforcer.class</name>
<value>datawave.policy.IngestPolicyEnforcer$NoOpIngestPolicyEnforcer</value>
<description>Name of the class to use for policy enforcement.
(1) datawave.policy.IngestPolicyEnforcer$NoOpIngestPolicyEnforcer will assume all records are valid.
(2) datawave.policy.ExampleIngestPolicyEnforcer will perform some validations that you'd probably want
to enforce for all data in a production deployment
</description>
</property>
<property>
<name>all.date.index.type.to.field.map</name>
<value>LOADED=LOAD_DATE,ACTIVITY=EVENT_DATE</value>
</property>
</configuration>