+1 sounds good.

On Fri, Feb 12, 2016 at 1:30 PM, Achim Nierbeck <[email protected]> wrote:
> Sounds OK to me.
>
> +1
>
> Regards, Achim
>
> sent from mobile device
> Am 12.02.2016 4:31 nachm. schrieb "Morgan Hautman" <[email protected]
>>:
>
>> +1
>> On Feb 12, 2016 15:47, "Andrea Cosentino" <[email protected]>
>> wrote:
>>
>> > It makes sense.
>> >
>> > +1 (non-binding).
>> >  --
>> > Andrea Cosentino
>> > ----------------------------------
>> > Apache Camel PMC Member
>> > Apache Karaf Committer
>> > Email: [email protected]
>> > Twitter: @oscerd2
>> > Github: oscerd
>> >
>> >
>> >
>> > On Friday, February 12, 2016 3:31 PM, Jean-Baptiste Onofré <
>> > [email protected]> wrote:
>> > Hi guys,
>> >
>> > I'm doing deeper and larger test on Decanter with Elasticsearch 1.x and
>> > 2.x, with the "new" elasticsearch rest appender.
>> >
>> > Unfortunately, elasticsearch 2.x introduced an important change compare
>> > to elasticsearch 1.x: '.' is no more allowed in field name.
>> > So, it means that field name like bundle.id or event.topics block fail
>> > the storage of the document in elasticsearch.
>> >
>> > In order to support both Elasticsearch 1.x and Elasticsearch 2.x, I
>> > would like to replace '.' by '_' in all field name (in the decanter
>> > marshaller).
>> >
>> > If it doesn't affect the default Kibana dashboards (they use the field
>> > values, not the name), it could have an impact for users who extended
>> > decanter.
>> >
>> > That's why I would propose the following:
>> > 1. I create the decanter-1.0.x branch based on the decanter-1.0.1 tag
>> > 2. I update decanter master to 1.1.0-SNAPSHOT version
>> > 3. then I will release Decanter 1.1.0 including support of elasticsearch
>> > 1.x and 2.x (with both native and REST API), and the other appenders
>> > (kafka, mqtt, etc).
>> >
>> > Thoughts ?
>> >
>> > Regards
>> > JB
>> > --
>> > Jean-Baptiste Onofré
>> > [email protected]
>> > http://blog.nanthrax.net
>> > Talend - http://www.talend.com
>> >
>>

Reply via email to