[overlord-issues] [JBoss JIRA] (RTGOV-520) Set "not_analyzed" as the default setting for fields added to rtgov.

[ivan mckinley (JIRA)]

     [ https://issues.jboss.org/browse/RTGOV-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ivan mckinley updated RTGOV-520:
--------------------------------

    Description: 
In rtgov-mapping.json. have the mapping set all fields to Not_analyzed. this avoids the issue outlined  in https://issues.jboss.org/browse/RTGOV-461
in there are mappings that required the field to be analyzed then they should be explicitly configured. 


  was:
As discussed in forum post (point 3), as the ElasticSearch capabilities are now encapsulated in the KeyValueStore implementation, it makes sense to make the EventProcessor more generic to cater for any key/store implementation.

As pointed out by Ivan, some custom capabilities may be required by particular KeyValueStore implementations (e.g. MongoDB, Cassandra), but these can be added later as extensions to the generic event processor.



> Set "not_analyzed" as the default setting for fields added to rtgov. 
> ---------------------------------------------------------------------
>
>                 Key: RTGOV-520
>                 URL: https://issues.jboss.org/browse/RTGOV-520
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: ivan mckinley
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>
> In rtgov-mapping.json. have the mapping set all fields to Not_analyzed. this avoids the issue outlined  in https://issues.jboss.org/browse/RTGOV-461
> in there are mappings that required the field to be analyzed then they should be explicitly configured. 



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)