[jira] [Updated] (KARAF-5793) Provide an option replace the dot or not in json field in the JsonMarshaller
[
https://issues.apache.org/jira/browse/KARAF-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-5793:
Fix Version/s: decanter-2.1.0
> Provide an option replace the dot or not in json field in the JsonMarshaller
>
>
> Key: KARAF-5793
> URL: https://issues.apache.org/jira/browse/KARAF-5793
> Project: Karaf
> Issue Type: Improvement
> Components: decanter
>Affects Versions: decanter-2.0.0
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: decanter-2.1.0
>
>
> The dot "." is replaced by "_" in json fields after changes from KARAF-4295.
> The reason could be that the field names containing dots will be rejected in
> ES 2.x (https://github.com/elastic/elasticsearch/issues/15951). but ES 5.x,
> 6.x support it again (parse it as Object). see
> https://www.elastic.co/guide/en/elasticsearch/reference/2.4/dots-in-names.html#_enabling_support_for_dots_in_field_names
> . Also there is an ENV option provided by ES to allow dots in the field
> name:
> {code}
> export ES_JAVA_OPTS="-Dmapper.allow_dots_in_name=true"
> {code}
> To give more compatibility and flexibility to the user, we may provide an
> option "replaceDotInFields=true/false" for the Json Marshaller. for now any
> custom fields name with "." woud be replaced by "_" silently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KARAF-5793) Provide an option replace the dot or not in json field in the JsonMarshaller
[
https://issues.apache.org/jira/browse/KARAF-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned KARAF-5793:
---
Assignee: Jean-Baptiste Onofré
> Provide an option replace the dot or not in json field in the JsonMarshaller
>
>
> Key: KARAF-5793
> URL: https://issues.apache.org/jira/browse/KARAF-5793
> Project: Karaf
> Issue Type: Improvement
> Components: decanter
>Affects Versions: decanter-2.0.0
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> The dot "." is replaced by "_" in json fields after changes from KARAF-4295.
> The reason could be that the field names containing dots will be rejected in
> ES 2.x (https://github.com/elastic/elasticsearch/issues/15951). but ES 5.x,
> 6.x support it again (parse it as Object). see
> https://www.elastic.co/guide/en/elasticsearch/reference/2.4/dots-in-names.html#_enabling_support_for_dots_in_field_names
> . Also there is an ENV option provided by ES to allow dots in the field
> name:
> {code}
> export ES_JAVA_OPTS="-Dmapper.allow_dots_in_name=true"
> {code}
> To give more compatibility and flexibility to the user, we may provide an
> option "replaceDotInFields=true/false" for the Json Marshaller. for now any
> custom fields name with "." woud be replaced by "_" silently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-5864) Be able to define property value type in system collector
Jean-Baptiste Onofré created KARAF-5864:
---
Summary: Be able to define property value type in system collector
Key: KARAF-5864
URL: https://issues.apache.org/jira/browse/KARAF-5864
Project: Karaf
Issue Type: Improvement
Components: decanter
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Fix For: decanter-2.1.0
Now, the system collector executes commands and get the command output as
{{String}} in the EventAdmin event.
It would be great to be able to try scalar type before fallbacking to
{{String}} or define the property type in {{cfg}} file:
{code}
command.foo.long=foo
command.foo.integer=foo
command.foo.string=foo
command.foo=foo // String as today
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
