[jira] [Updated] (PYLUCENE-52) JCC build fails with Python 3.8.
[
https://issues.apache.org/jira/browse/PYLUCENE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Allouche updated PYLUCENE-52:
---
Attachment: pylucene-lpython.patch
> JCC build fails with Python 3.8.
>
>
> Key: PYLUCENE-52
> URL: https://issues.apache.org/jira/browse/PYLUCENE-52
> Project: PyLucene
> Issue Type: Bug
> Environment: linux
>Reporter: A. Coady
>Priority: Major
> Attachments: pylucene-lpython.patch
>
>
> JCC build fails with
> {{/usr/bin/ld: cannot find -lpython3.8m}}
> because 3.8 dropped the m flag.
> https://docs.python.org/3.8/whatsnew/3.8.html#build-and-c-api-changes
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (PYLUCENE-52) JCC build fails with Python 3.8.
[
https://issues.apache.org/jira/browse/PYLUCENE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17445964#comment-17445964
]
David Allouche commented on PYLUCENE-52:
Apply this patch to compile lucene with python>=3.8.
[^pylucene-lpython.patch]
> JCC build fails with Python 3.8.
>
>
> Key: PYLUCENE-52
> URL: https://issues.apache.org/jira/browse/PYLUCENE-52
> Project: PyLucene
> Issue Type: Bug
> Environment: linux
>Reporter: A. Coady
>Priority: Major
> Attachments: pylucene-lpython.patch
>
>
> JCC build fails with
> {{/usr/bin/ld: cannot find -lpython3.8m}}
> because 3.8 dropped the m flag.
> https://docs.python.org/3.8/whatsnew/3.8.html#build-and-c-api-changes
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
Re: [VOTE] Release PyLucene 8.1.1
> On 17 Jun 2019, at 20:42, Andi Vajda wrote: > > > On Mon, 17 Jun 2019, David Allouche wrote: > >> Thank you, that was very informative. >> >> +0 for this release, I builds and pass my test suite. >> >> But I was unable to make a complete integration test because I do not have a >> proper index format migration infrastructure and my index is made of >> incompletely-upgraded lucene6 and lucene7 segments. > > So far, you're the only one who has cast a vote. > No one else, no PMC member, none of the longtime users, no one. Marc Jeurissen did +1. Message-Id: <5cff4939.1c69fb81.2d212.8174smtpin_added_miss...@mx.google.com> And since you posted your message, Milo H Fields III did +0. So there _is_ interest. I do have a long-term need for PyLucene, but I really just need one release per major version to have an index upgrade path. But it seems like Lucene Core make major releases quite frequently nowadays.
Re: [VOTE] Release PyLucene 8.1.1
Thank you, that was very informative. +0 for this release, I builds and pass my test suite. But I was unable to make a complete integration test because I do not have a proper index format migration infrastructure and my index is made of incompletely-upgraded lucene6 and lucene7 segments. I will post my questions about index upgrading on java-u...@lucene.apache.org <mailto:java-u...@lucene.apache.org>. Regards. > On 11 Jun 2019, at 16:50, Andi Vajda wrote: > > >> On Jun 11, 2019, at 06:30, David Allouche wrote: >> >> This is maybe a silly question, but what is the purpose of this voting >> process? > > By the rules of Apache, three PMC binding votes are needed to make a release. > In addition, it's a gauge of general interest in the project. > >> Is this something required by the project governance? > > https://www.apache.org/foundation/voting.html > (see "votes on package releases", in particular) > >> What is the meaning of a vote? Does that mean "I am interested", or does it >> mean "I have tested the latest trunk and it looks good", or something else? > > If you find a bug in the release artifacts (not in the latest trunk) before > the release is made, the release is likely to be pulled. > >> What is the typical expected delay for reply? For example, I reserve Fridays >> for technical debt management (including upgrading dependencies), so I >> cannot typically validate a new PyLucene version in less than a week. > > A vote must run for at least 72 hours. > Because you are not on the PMC, your vote falls into the "interest gauging" > category, is not binding and is considered "best effort". > >> This is probably all common questions with well documented answers. If >> that's the case, then it would be nice to have a link to the answers in VOTE >> requests. > > https://www.apache.org/foundation/voting.html > > Andi.. > >> >>> On 11 Jun 2019, at 00:39, Andi Vajda wrote: >>> >>> >>> The PyLucene 8.1.1 (rc1) release tracking the recent release of >>> Apache Lucene 8.1.1 is ready. >>> >>> A release candidate is available from: >>> https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/ >>> >>> PyLucene 8.1.1 is built with JCC 3.5, included in these release artifacts. >>> >>> JCC 3.5 supports Python 3.3+ (in addition to Python 2.3+). >>> PyLucene may be built with Python 2 or Python 3. >>> >>> Please vote to release these artifacts as PyLucene 8.1.1. >>> Anyone interested in this release can and should vote ! >>> >>> Thanks ! >>> >>> Andi.. >>> >>> ps: the KEYS file for PyLucene release signing is at: >>> https://dist.apache.org/repos/dist/release/lucene/pylucene/KEYS >>> https://dist.apache.org/repos/dist/dev/lucene/pylucene/KEYS >>> >>> pps: here is my +1 >>
Re: [VOTE] Release PyLucene 8.1.1
This is maybe a silly question, but what is the purpose of this voting process? Is this something required by the project governance? What is the meaning of a vote? Does that mean "I am interested", or does it mean "I have tested the latest trunk and it looks good", or something else? What is the typical expected delay for reply? For example, I reserve Fridays for technical debt management (including upgrading dependencies), so I cannot typically validate a new PyLucene version in less than a week. This is probably all common questions with well documented answers. If that's the case, then it would be nice to have a link to the answers in VOTE requests. > On 11 Jun 2019, at 00:39, Andi Vajda wrote: > > > The PyLucene 8.1.1 (rc1) release tracking the recent release of > Apache Lucene 8.1.1 is ready. > > A release candidate is available from: > https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.1.1-rc1/ > > PyLucene 8.1.1 is built with JCC 3.5, included in these release artifacts. > > JCC 3.5 supports Python 3.3+ (in addition to Python 2.3+). > PyLucene may be built with Python 2 or Python 3. > > Please vote to release these artifacts as PyLucene 8.1.1. > Anyone interested in this release can and should vote ! > > Thanks ! > > Andi.. > > ps: the KEYS file for PyLucene release signing is at: > https://dist.apache.org/repos/dist/release/lucene/pylucene/KEYS > https://dist.apache.org/repos/dist/dev/lucene/pylucene/KEYS > > pps: here is my +1
Re: java.lang.IllegalArgumentException: Could not load codec 'Lucene62'. Did you forget to add lucene-backward-codecs.jar?
Thank you Andi, you're awesome! > On 5 Jun 2019, at 00:33, Andi Vajda wrote: > > > In rev 1860637 I refreshed the list of supported lucene module to be built > with PyLucene. The lucene-backward-codecs module was indeed missing. > > Please, try it out with pylucene 7.7.1 (refresing its Makefile from trunk) > and let me know if it fixes your problem. > > Thanks ! > > Andi.. > > On Tue, 4 Jun 2019, David Allouche wrote: > >> Hello, >> >> I use pylucene, and I am upgrading from 6.5.0 to 7.7.1. >> >> Opening my old index using the new pylucene, I get >> >>> Traceback (most recent call last): >>> ... >>> File "/home/user/jobaffinity/lib/luceneindex.py", line 58, in >>> create_lucene_index_maybe >>>writer = IndexWriter(directory, config) >>> lucene.JavaError: , > >>>Java stacktrace: >>> java.lang.IllegalArgumentException: Could not load codec 'Lucene62'. Did >>> you forget to add lucene-backward-codecs.jar? >>>at org.apache.lucene.index.SegmentInfos.readCodec(SegmentInfos.java:428) >>>at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:360) >>>at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:291) >>>at org.apache.lucene.index.IndexWriter.(IndexWriter.java:845) >>> Caused by: java.lang.IllegalArgumentException: An SPI class of type >>> org.apache.lucene.codecs.Codec with name 'Lucene62' does not exist. You >>> need to add the corresponding JAR file supporting this SPI to your >>> classpath. The current classpath supports the following names: [Lucene70] >>>at org.apache.lucene.util.NamedSPILoader.lookup(NamedSPILoader.java:116) >>>at org.apache.lucene.codecs.Codec.forName(Codec.java:116) >>>at org.apache.lucene.index.SegmentInfos.readCodec(SegmentInfos.java:424) >>>... 3 more >> >> I am really not familiar with the Java side of things. With some help from >> the web, I found out where to download the jars. >> >> I presume I need >> http://central.maven.org/maven2/org/apache/lucene/lucene-backward-codecs/7.7.1/lucene-backward-codecs-7.7.1.jar >> >> But then, I am quite clueless about what to do. I tried dumping the jar >> right next to lucene-core-7.7.1.jar, in my >> $(VENV)/lib/python2.7/site-packages/lucene, but that does not seem to help. >> >> I have a large-ish index with about 22M entries, used in a public-facing >> service, so I very much like to avoid rebuilding the index every time I >> upgrade pylucene. >> >> I could reverse-engineer this script: >> https://github.com/cominvent/solr-tools/blob/master/upgradeindex/upgradeindex.sh >> >> But that would require me to put the service down while running the >> migration. >> >> How can I package the lucene-backwards-codecs in pylucene? >> >> >>
java.lang.IllegalArgumentException: Could not load codec 'Lucene62'. Did you forget to add lucene-backward-codecs.jar?
Hello, I use pylucene, and I am upgrading from 6.5.0 to 7.7.1. Opening my old index using the new pylucene, I get > Traceback (most recent call last): > ... > File "/home/user/jobaffinity/lib/luceneindex.py", line 58, in > create_lucene_index_maybe > writer = IndexWriter(directory, config) > lucene.JavaError: , > > Java stacktrace: > java.lang.IllegalArgumentException: Could not load codec 'Lucene62'. Did you > forget to add lucene-backward-codecs.jar? > at org.apache.lucene.index.SegmentInfos.readCodec(SegmentInfos.java:428) > at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:360) > at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:291) > at org.apache.lucene.index.IndexWriter.(IndexWriter.java:845) > Caused by: java.lang.IllegalArgumentException: An SPI class of type > org.apache.lucene.codecs.Codec with name 'Lucene62' does not exist. You need > to add the corresponding JAR file supporting this SPI to your classpath. The > current classpath supports the following names: [Lucene70] > at org.apache.lucene.util.NamedSPILoader.lookup(NamedSPILoader.java:116) > at org.apache.lucene.codecs.Codec.forName(Codec.java:116) > at org.apache.lucene.index.SegmentInfos.readCodec(SegmentInfos.java:424) > ... 3 more I am really not familiar with the Java side of things. With some help from the web, I found out where to download the jars. I presume I need http://central.maven.org/maven2/org/apache/lucene/lucene-backward-codecs/7.7.1/lucene-backward-codecs-7.7.1.jar But then, I am quite clueless about what to do. I tried dumping the jar right next to lucene-core-7.7.1.jar, in my $(VENV)/lib/python2.7/site-packages/lucene, but that does not seem to help. I have a large-ish index with about 22M entries, used in a public-facing service, so I very much like to avoid rebuilding the index every time I upgrade pylucene. I could reverse-engineer this script: https://github.com/cominvent/solr-tools/blob/master/upgradeindex/upgradeindex.sh But that would require me to put the service down while running the migration. How can I package the lucene-backwards-codecs in pylucene?
