You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2016/02/12 15:31:28 UTC
[DISCUSS] Release Decanter 1.1.0
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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [DISCUSS] Release Decanter 1.1.0
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi all,
Last Sunday and yesterday, I added full support of Elasticsearch 2.x and
Kibana 4.x (features and appenders).
However, ServiceMix elasticsearch 2.x bundles contained some issues that
I had to fix. I submit a ServiceMix bundles release to vote yesterday
that we need for Decanter 1.1.0 release.
So, I postpone Decanter 1.1.0 release vote to March, 5th (after my
vacations, as I will be off from Friday to March, 4th. I will have an
Internet connection, but a bit limited).
Regards
JB
On 02/12/2016 03:31 PM, Jean-Baptiste Onofré 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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [DISCUSS] Release Decanter 1.1.0
Posted by "Jamie G." <ja...@gmail.com>.
+1 sounds good.
On Fri, Feb 12, 2016 at 1:30 PM, Achim Nierbeck <bc...@googlemail.com> wrote:
> Sounds OK to me.
>
> +1
>
> Regards, Achim
>
> sent from mobile device
> Am 12.02.2016 4:31 nachm. schrieb "Morgan Hautman" <morgan.hautman@gmail.com
>>:
>
>> +1
>> On Feb 12, 2016 15:47, "Andrea Cosentino" <an...@yahoo.com.invalid>
>> wrote:
>>
>> > It makes sense.
>> >
>> > +1 (non-binding).
>> > --
>> > Andrea Cosentino
>> > ----------------------------------
>> > Apache Camel PMC Member
>> > Apache Karaf Committer
>> > Email: ancosen1985@yahoo.com
>> > Twitter: @oscerd2
>> > Github: oscerd
>> >
>> >
>> >
>> > On Friday, February 12, 2016 3:31 PM, Jean-Baptiste Onofré <
>> > jb@nanthrax.net> 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é
>> > jbonofre@apache.org
>> > http://blog.nanthrax.net
>> > Talend - http://www.talend.com
>> >
>>
Re: [DISCUSS] Release Decanter 1.1.0
Posted by Achim Nierbeck <bc...@googlemail.com>.
Sounds OK to me.
+1
Regards, Achim
sent from mobile device
Am 12.02.2016 4:31 nachm. schrieb "Morgan Hautman" <morgan.hautman@gmail.com
>:
> +1
> On Feb 12, 2016 15:47, "Andrea Cosentino" <an...@yahoo.com.invalid>
> wrote:
>
> > It makes sense.
> >
> > +1 (non-binding).
> > --
> > Andrea Cosentino
> > ----------------------------------
> > Apache Camel PMC Member
> > Apache Karaf Committer
> > Email: ancosen1985@yahoo.com
> > Twitter: @oscerd2
> > Github: oscerd
> >
> >
> >
> > On Friday, February 12, 2016 3:31 PM, Jean-Baptiste Onofré <
> > jb@nanthrax.net> 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é
> > jbonofre@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
Re: [DISCUSS] Release Decanter 1.1.0
Posted by Morgan Hautman <mo...@gmail.com>.
+1
On Feb 12, 2016 15:47, "Andrea Cosentino" <an...@yahoo.com.invalid>
wrote:
> It makes sense.
>
> +1 (non-binding).
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Member
> Apache Karaf Committer
> Email: ancosen1985@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
> On Friday, February 12, 2016 3:31 PM, Jean-Baptiste Onofré <
> jb@nanthrax.net> 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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [DISCUSS] Release Decanter 1.1.0
Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.
It makes sense.
+1 (non-binding).
--
Andrea Cosentino
----------------------------------
Apache Camel PMC Member
Apache Karaf Committer
Email: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Friday, February 12, 2016 3:31 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> 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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com