Upgrade dependency to outdated Lucene 3.5.0

[Andrew Mashenkov]

Hi Igniters,

Ignite-indexing module has outdated dependency to apache-lucene-3.5.0,
however, actual version of lucene for now is 6.5.1. Here is a ticket [1].

Store format version of 3.x is deprecated in 4.x and does not supported at
all
in higher versions, that cause difficulties to integrate with ignite on
user side.

Apache Lucene 6.x seems doen't support <=4.x index format,
but 5.x index format can be used via additional jar with old codecs.

Also, I've found GridLuceneIndex stores index in offheap via old approach
and
page memory is not supported, so it can't be persisted (looking forward to
PDS).

Seems, we will not break any compatibility if we upgrade lucene version in
2.1,
until (or together with) Ignite full-text-search component supports page
memory and PDS merged to ignite.
I think we should upgrade to latest 6.x version, as it will much harder to
do it later.


Is there any cons\pros to upgrade lucene dependency up to latest 6.x
version?


[1] https://issues.apache.org/jira/browse/IGNITE-3562

--
Best regards,
Andrey V. Mashenkov

Lucene6 requires JDK8 and later versions, and I think it might be
reasonable to update to the Lucene5.5.4 version.


在 2017/5/23 22:07, Andrey Mashenkov 写道:

> Hi Igniters,
>
> Ignite-indexing module has outdated dependency to apache-lucene-3.5.0,
> however, actual version of lucene for now is 6.5.1. Here is a ticket [1].
>
> Store format version of 3.x is deprecated in 4.x and does not supported at
> all
> in higher versions, that cause difficulties to integrate with ignite on
> user side.
>
> Apache Lucene 6.x seems doen't support <=4.x index format,
> but 5.x index format can be used via additional jar with old codecs.
>
> Also, I've found GridLuceneIndex stores index in offheap via old approach
> and
> page memory is not supported, so it can't be persisted (looking forward to
> PDS).
>
> Seems, we will not break any compatibility if we upgrade lucene version in
> 2.1,
> until (or together with) Ignite full-text-search component supports page
> memory and PDS merged to ignite.
> I think we should upgrade to latest 6.x version, as it will much harder to
> do it later.
>
>
> Is there any cons\pros to upgrade lucene dependency up to latest 6.x
> version?
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-3562
>

[Andrew Mashenkov]

Thanks. This fact was missed in migration guide.

We have dependency to lucene in our osgi module, that refer to Apache
ServiceMix :: Bundles  [1] .
I can't see bundle for Lucene-5.5.4 in list, but there is a bundle for
Lucene-5.5.2.

Let's upgrade to Lucene-5.5.2.

[1]
https://mvnrepository.com/artifact/org.apache.servicemix.bundles/org.apache.servicemix.bundles.lucene


On Tue, May 23, 2017 at 6:07 PM, 李玉珏@163 <[hidden email]> wrote:

> Lucene6 requires JDK8 and later versions, and I think it might be
> reasonable to update to the Lucene5.5.4 version.
>
>
>
> 在 2017/5/23 22:07, Andrey Mashenkov 写道:
>
>> Hi Igniters,
>>
>> Ignite-indexing module has outdated dependency to apache-lucene-3.5.0,
>> however, actual version of lucene for now is 6.5.1. Here is a ticket [1].
>>
>> Store format version of 3.x is deprecated in 4.x and does not supported at
>> all
>> in higher versions, that cause difficulties to integrate with ignite on
>> user side.
>>
>> Apache Lucene 6.x seems doen't support <=4.x index format,
>> but 5.x index format can be used via additional jar with old codecs.
>>
>> Also, I've found GridLuceneIndex stores index in offheap via old approach
>> and
>> page memory is not supported, so it can't be persisted (looking forward to
>> PDS).
>>
>> Seems, we will not break any compatibility if we upgrade lucene version in
>> 2.1,
>> until (or together with) Ignite full-text-search component supports page
>> memory and PDS merged to ignite.
>> I think we should upgrade to latest 6.x version, as it will much harder to
>> do it later.
>>
>>
>> Is there any cons\pros to upgrade lucene dependency up to latest 6.x
>> version?
>>
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-3562
>>
>>
>
>

--
Best regards,
Andrey V. Mashenkov

[Sergey Kozlov]

Hi Andrey

I see 5.5.4 in maven repository
https://mvnrepository.com/artifact/org.apache.lucene/lucene-core/5.5.4

On Tue, May 23, 2017 at 6:48 PM, Andrey Mashenkov <
[hidden email]> wrote:

> Thanks. This fact was missed in migration guide.
>
> We have dependency to lucene in our osgi module, that refer to Apache
> ServiceMix :: Bundles  [1] .
> I can't see bundle for Lucene-5.5.4 in list, but there is a bundle for
> Lucene-5.5.2.
>
> Let's upgrade to Lucene-5.5.2.
>
> [1]
> https://mvnrepository.com/artifact/org.apache.
> servicemix.bundles/org.apache.servicemix.bundles.lucene
>
>
> On Tue, May 23, 2017 at 6:07 PM, 李玉珏@163 <[hidden email]> wrote:
>
> > Lucene6 requires JDK8 and later versions, and I think it might be
> > reasonable to update to the Lucene5.5.4 version.
> >
> >
> >
> > 在 2017/5/23 22:07, Andrey Mashenkov 写道:
> >
> >> Hi Igniters,
> >>
> >> Ignite-indexing module has outdated dependency to apache-lucene-3.5.0,
> >> however, actual version of lucene for now is 6.5.1. Here is a ticket
> [1].
> >>
> >> Store format version of 3.x is deprecated in 4.x and does not supported
> at
> >> all
> >> in higher versions, that cause difficulties to integrate with ignite on
> >> user side.
> >>
> >> Apache Lucene 6.x seems doen't support <=4.x index format,
> >> but 5.x index format can be used via additional jar with old codecs.
> >>
> >> Also, I've found GridLuceneIndex stores index in offheap via old
> approach
> >> and
> >> page memory is not supported, so it can't be persisted (looking forward
> to
> >> PDS).
> >>
> >> Seems, we will not break any compatibility if we upgrade lucene version
> in
> >> 2.1,
> >> until (or together with) Ignite full-text-search component supports page
> >> memory and PDS merged to ignite.
> >> I think we should upgrade to latest 6.x version, as it will much harder
> to
> >> do it later.
> >>
> >>
> >> Is there any cons\pros to upgrade lucene dependency up to latest 6.x
> >> version?
> >>
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-3562
> >>
> >>
> >
> >
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>

--
Sergey Kozlov
GridGain Systems
www.gridgain.com

[Andrew Mashenkov]

Hi Sergey,

Yes, lucene 5.5.4 jars are present in maven repository, but no
Apache-ServiceMix bundle for 5.5.4.
It is used by ignite-osgi-karaf module. See feature configuration with
name="ignite-indexing" in modules/osgi-karaf/src/main/resources/feature.xml


On Tue, May 23, 2017 at 6:59 PM, Sergey Kozlov <[hidden email]> wrote:

> Hi Andrey
>
> I see 5.5.4 in maven repository
> https://mvnrepository.com/artifact/org.apache.lucene/lucene-core/5.5.4
>
> On Tue, May 23, 2017 at 6:48 PM, Andrey Mashenkov <
> [hidden email]> wrote:
>
> > Thanks. This fact was missed in migration guide.
> >
> > We have dependency to lucene in our osgi module, that refer to Apache
> > ServiceMix :: Bundles  [1] .
> > I can't see bundle for Lucene-5.5.4 in list, but there is a bundle for
> > Lucene-5.5.2.
> >
> > Let's upgrade to Lucene-5.5.2.
> >
> > [1]
> > https://mvnrepository.com/artifact/org.apache.
> > servicemix.bundles/org.apache.servicemix.bundles.lucene
> >
> >
> > On Tue, May 23, 2017 at 6:07 PM, 李玉珏@163 <[hidden email]> wrote:
> >
> > > Lucene6 requires JDK8 and later versions, and I think it might be
> > > reasonable to update to the Lucene5.5.4 version.
> > >
> > >
> > >
> > > 在 2017/5/23 22:07, Andrey Mashenkov 写道:
> > >
> > >> Hi Igniters,
> > >>
> > >> Ignite-indexing module has outdated dependency to apache-lucene-3.5.0,
> > >> however, actual version of lucene for now is 6.5.1. Here is a ticket
> > [1].
> > >>
> > >> Store format version of 3.x is deprecated in 4.x and does not
> supported
> > at
> > >> all
> > >> in higher versions, that cause difficulties to integrate with ignite
> on
> > >> user side.
> > >>
> > >> Apache Lucene 6.x seems doen't support <=4.x index format,
> > >> but 5.x index format can be used via additional jar with old codecs.
> > >>
> > >> Also, I've found GridLuceneIndex stores index in offheap via old
> > approach
> > >> and
> > >> page memory is not supported, so it can't be persisted (looking
> forward
> > to
> > >> PDS).
> > >>
> > >> Seems, we will not break any compatibility if we upgrade lucene
> version
> > in
> > >> 2.1,
> > >> until (or together with) Ignite full-text-search component supports
> page
> > >> memory and PDS merged to ignite.
> > >> I think we should upgrade to latest 6.x version, as it will much
> harder
> > to
> > >> do it later.
> > >>
> > >>
> > >> Is there any cons\pros to upgrade lucene dependency up to latest 6.x
> > >> version?
> > >>
> > >>
> > >> [1] https://issues.apache.org/jira/browse/IGNITE-3562
> > >>
> > >>
> > >
> > >
> >
> >
> > --
> > Best regards,
> > Andrey V. Mashenkov
> >
>
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com
>

--
Best regards,
Andrey V. Mashenkov

[Andrew Mashenkov]

Guys,

IGNITE-3562 [1] is ready for review. Upsource review link is attached to
the ticket.
Would someone please handle it?

[1] https://issues.apache.org/jira/browse/IGNITE-3562

On Tue, May 23, 2017 at 8:21 PM, Andrey Mashenkov <
[hidden email]> wrote:

> Hi Sergey,
>
> Yes, lucene 5.5.4 jars are present in maven repository, but no
> Apache-ServiceMix bundle for 5.5.4.
> It is used by ignite-osgi-karaf module. See feature configuration with
> name="ignite-indexing" in modules/osgi-karaf/src/
> main/resources/feature.xml
>
>
> On Tue, May 23, 2017 at 6:59 PM, Sergey Kozlov <[hidden email]>
> wrote:
>
>> Hi Andrey
>>
>> I see 5.5.4 in maven repository
>> https://mvnrepository.com/artifact/org.apache.lucene/lucene-core/5.5.4
>>
>> On Tue, May 23, 2017 at 6:48 PM, Andrey Mashenkov <
>> [hidden email]> wrote:
>>
>> > Thanks. This fact was missed in migration guide.
>> >
>> > We have dependency to lucene in our osgi module, that refer to Apache
>> > ServiceMix :: Bundles  [1] .
>> > I can't see bundle for Lucene-5.5.4 in list, but there is a bundle for
>> > Lucene-5.5.2.
>> >
>> > Let's upgrade to Lucene-5.5.2.
>> >
>> > [1]
>> > https://mvnrepository.com/artifact/org.apache.
>> > servicemix.bundles/org.apache.servicemix.bundles.lucene
>> >
>> >
>> > On Tue, May 23, 2017 at 6:07 PM, 李玉珏@163 <[hidden email]> wrote:
>> >
>> > > Lucene6 requires JDK8 and later versions, and I think it might be
>> > > reasonable to update to the Lucene5.5.4 version.
>> > >
>> > >
>> > >
>> > > 在 2017/5/23 22:07, Andrey Mashenkov 写道:
>> > >
>> > >> Hi Igniters,
>> > >>
>> > >> Ignite-indexing module has outdated dependency to
>> apache-lucene-3.5.0,
>> > >> however, actual version of lucene for now is 6.5.1. Here is a ticket
>> > [1].
>> > >>
>> > >> Store format version of 3.x is deprecated in 4.x and does not
>> supported
>> > at
>> > >> all
>> > >> in higher versions, that cause difficulties to integrate with ignite
>> on
>> > >> user side.
>> > >>
>> > >> Apache Lucene 6.x seems doen't support <=4.x index format,
>> > >> but 5.x index format can be used via additional jar with old codecs.
>> > >>
>> > >> Also, I've found GridLuceneIndex stores index in offheap via old
>> > approach
>> > >> and
>> > >> page memory is not supported, so it can't be persisted (looking
>> forward
>> > to
>> > >> PDS).
>> > >>
>> > >> Seems, we will not break any compatibility if we upgrade lucene
>> version
>> > in
>> > >> 2.1,
>> > >> until (or together with) Ignite full-text-search component supports
>> page
>> > >> memory and PDS merged to ignite.
>> > >> I think we should upgrade to latest 6.x version, as it will much
>> harder
>> > to
>> > >> do it later.
>> > >>
>> > >>
>> > >> Is there any cons\pros to upgrade lucene dependency up to latest 6.x
>> > >> version?
>> > >>
>> > >>
>> > >> [1] https://issues.apache.org/jira/browse/IGNITE-3562
>> > >>
>> > >>
>> > >
>> > >
>> >
>> >
>> > --
>> > Best regards,
>> > Andrey V. Mashenkov
>> >
>>
>>
>>
>> --
>> Sergey Kozlov
>> GridGain Systems
>> www.gridgain.com
>>
>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>

--
Best regards,
Andrey V. Mashenkov