Re: [POLL] What should happen to PyLucene now?

[Andi Vajda]

On Mon, 5 Sep 2016, Dirk Rothe wrote:


Am 03.09.2016, 18:34 Uhr, schrieb Andi Vajda :


Here is how one can reproduce what I just did:
- cd ~/apache
- git clone --branch branch_6x https://github.com/apache/lucene-solr.git 
lucene.6x

- cd 
- svn update
  make sure you have a modern setuptools (if you are on linux, the
  setuptools patching done by JCC to be able to build a plain shared
  library most likely needs to be refreshed or maybe even eliminated).
- _install/bin/pip uninstall setuptools
- _install/bin/pip install setuptools
- cd jcc
- ../_install/bin/python setup.py build install
- cd ..
- make sources (this copies the lucene tree from the github tree cloned)
- make compile install

If all worked, you can then:
- _install/bin/python
>>> import lucene
>>> lucene.initVM()
- _install/bin/python test/test_Binary.py

I have a Python virtual env installed in pylucene/_install, this helps 
with keeping different versions of software separate.



2. Volunteers should then help in porting old 4.x tests, if they still
   apply, and import new tests from the current Lucene suite as they see
   fit.


All other tests need to be carefully ported to match all the numerous API 
changes and disappeared classes. For similar reasons, the extensions jar 
does not build and is not currently included in the build. Its source java 
classes need to be refreshed as tests get refreshed to 6.x.


PyLucene now builds and passes all its tests on Mac OS X and Linux.
It is thus in a state where a release candidate could be built and 
submitted for review.


A volunteer is requested to build and test PyLucene's trunk on Windows. If 
noone comes forward, I intend to try to release PyLucene 6.2 in a few 
weeks, still.


Nice Job!

I've successfully build PyLucene 6.2 on windows. Most tests pass:
* skipped the three test_ICU* due to missing "import icu"


Yes, for this you need to install PyICU: https://github.com/ovalhub/pyicu

* fixed test_PyLucene.py by ignoring open file handles (os.error) in 
shutil.rmtree() in Test_PyLuceneWithFSStore.tearDown()


Do you have a patch for me to apply ?


* then stuff like these in test_PythonDirectory.py
==
ERROR: test_FieldEnumeration (__main__.PythonDirectoryTests)
--
Traceback (most recent call last):
File "D:\vls-lucene43\misc\pylucene_62\test\test_PyLucene.py", line 234, in 
test_FieldEnumeration

  self.test_indexDocument()
File "D:\vls-lucene43\misc\pylucene_62\test\test_PyLucene.py", line 86, in 
test_indexDocument

  self.closeStore(store, writer)
File "test_PythonDirectory.py", line 254, in closeStore
  arg.close()
JavaError: , >
  Java stacktrace:
java.lang.RuntimeException: InvalidArgsError
	at org.apache.pylucene.store.PythonDirectory.deleteFile(Native 
Method)
	at 
org.apache.lucene.store.LockValidatingDirectoryWrapper.deleteFile(LockValidatingDirectoryWrapper.java:38)
	at 
org.apache.lucene.index.IndexFileDeleter.deleteFile(IndexFileDeleter.java:721)
	at 
org.apache.lucene.index.IndexFileDeleter.deleteFiles(IndexFileDeleter.java:715)
	at 
org.apache.lucene.index.IndexFileDeleter.deleteNewFiles(IndexFileDeleter.java:691)
	at 
org.apache.lucene.index.IndexWriter.flushFailed(IndexWriter.java:4929)
	at 
org.apache.lucene.index.DocumentsWriter$FlushFailedEvent.process(DocumentsWriter.java:758)
	at 
org.apache.lucene.index.IndexWriter.processEvents(IndexWriter.java:4991)
	at 
org.apache.lucene.index.IndexWriter.processEvents(IndexWriter.java:4982)

at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java:3372)
at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java:)
	at 
org.apache.lucene.index.IndexWriter.shutdown(IndexWriter.java:1117)

at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1162)


Can't make sense of this one, sorry.


* and this one in test_PythonException.py
==
ERROR: testThroughLayerException (__main__.PythonExceptionTestCase)
--
Traceback (most recent call last):
File "test_PythonException.py", line 34, in testThroughLayerException
  qp.parse("foo bar")
JavaError: , >
  Java stacktrace:
java.lang.RuntimeException: TestException
	at 
org.apache.pylucene.queryparser.classic.PythonQueryParser.getFieldQuery_quoted(Native 
Method)
	at 
org.apache.pylucene.queryparser.classic.PythonQueryParser.getFieldQuery(Unknown 
Source)
	at 
org.apache.lucene.queryparser.classic.QueryParser.MultiTerm(QueryParser.java:585)
	at 
org.apache.lucene.queryparser.classic.QueryParser.Query(QueryParser.java:198)
	at 
org.apache.lucene.queryparser.classic.QueryParser.TopLevelQuery(QueryParser.java:187)
	at 
org.apache.lucene.queryparser.classic.QueryParserBase.parse(QueryParserBase.java:111)


This one could be because you may not have built JCC in shared mode ?
I vaguely

Re: [POLL] What should happen to PyLucene now?

[Dirk Rothe]

Am 03.09.2016, 18:34 Uhr, schrieb Andi Vajda :


Here is how one can reproduce what I just did:
 - cd ~/apache
 - git clone --branch branch_6x  
https://github.com/apache/lucene-solr.git lucene.6x

 - cd 
 - svn update
   make sure you have a modern setuptools (if you are on linux, the
   setuptools patching done by JCC to be able to build a plain shared
   library most likely needs to be refreshed or maybe even eliminated).
 - _install/bin/pip uninstall setuptools
 - _install/bin/pip install setuptools
 - cd jcc
 - ../_install/bin/python setup.py build install
 - cd ..
 - make sources (this copies the lucene tree from the github tree  
cloned)

 - make compile install

If all worked, you can then:
 - _install/bin/python
 >>> import lucene
 >>> lucene.initVM()
 - _install/bin/python test/test_Binary.py

I have a Python virtual env installed in pylucene/_install, this helps  
with keeping different versions of software separate.



 2. Volunteers should then help in porting old 4.x tests, if they still
apply, and import new tests from the current Lucene suite as they  
see

fit.


All other tests need to be carefully ported to match all the numerous  
API changes and disappeared classes. For similar reasons, the  
extensions jar does not build and is not currently included in the  
build. Its source java classes need to be refreshed as tests get  
refreshed to 6.x.


PyLucene now builds and passes all its tests on Mac OS X and Linux.
It is thus in a state where a release candidate could be built and  
submitted for review.


A volunteer is requested to build and test PyLucene's trunk on Windows.  
If noone comes forward, I intend to try to release PyLucene 6.2 in a few  
weeks, still.


Nice Job!

I've successfully build PyLucene 6.2 on windows. Most tests pass:
* skipped the three test_ICU* due to missing "import icu"
* fixed test_PyLucene.py by ignoring open file handles (os.error) in  
shutil.rmtree() in Test_PyLuceneWithFSStore.tearDown()


* then stuff like these in test_PythonDirectory.py
==
ERROR: test_FieldEnumeration (__main__.PythonDirectoryTests)
--
Traceback (most recent call last):
  File "D:\vls-lucene43\misc\pylucene_62\test\test_PyLucene.py", line 234,  
in test_FieldEnumeration

self.test_indexDocument()
  File "D:\vls-lucene43\misc\pylucene_62\test\test_PyLucene.py", line 86,  
in test_indexDocument

self.closeStore(store, writer)
  File "test_PythonDirectory.py", line 254, in closeStore
arg.close()
JavaError: , >
Java stacktrace:
java.lang.RuntimeException: InvalidArgsError
at org.apache.pylucene.store.PythonDirectory.deleteFile(Native Method)
	at  
org.apache.lucene.store.LockValidatingDirectoryWrapper.deleteFile(LockValidatingDirectoryWrapper.java:38)
	at  
org.apache.lucene.index.IndexFileDeleter.deleteFile(IndexFileDeleter.java:721)
	at  
org.apache.lucene.index.IndexFileDeleter.deleteFiles(IndexFileDeleter.java:715)
	at  
org.apache.lucene.index.IndexFileDeleter.deleteNewFiles(IndexFileDeleter.java:691)

at 
org.apache.lucene.index.IndexWriter.flushFailed(IndexWriter.java:4929)
	at  
org.apache.lucene.index.DocumentsWriter$FlushFailedEvent.process(DocumentsWriter.java:758)
	at  
org.apache.lucene.index.IndexWriter.processEvents(IndexWriter.java:4991)
	at  
org.apache.lucene.index.IndexWriter.processEvents(IndexWriter.java:4982)

at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java:3372)
at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java:)
at org.apache.lucene.index.IndexWriter.shutdown(IndexWriter.java:1117)
at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1162)

* and this one in test_PythonException.py
==
ERROR: testThroughLayerException (__main__.PythonExceptionTestCase)
--
Traceback (most recent call last):
  File "test_PythonException.py", line 34, in testThroughLayerException
qp.parse("foo bar")
JavaError: , >
Java stacktrace:
java.lang.RuntimeException: TestException
	at  
org.apache.pylucene.queryparser.classic.PythonQueryParser.getFieldQuery_quoted(Native  
Method)
	at  
org.apache.pylucene.queryparser.classic.PythonQueryParser.getFieldQuery(Unknown  
Source)
	at  
org.apache.lucene.queryparser.classic.QueryParser.MultiTerm(QueryParser.java:585)
	at  
org.apache.lucene.queryparser.classic.QueryParser.Query(QueryParser.java:198)
	at  
org.apache.lucene.queryparser.classic.QueryParser.TopLevelQuery(QueryParser.java:187)
	at  
org.apache.lucene.queryparser.classic.QueryParserBase.parse(QueryParserBase.java:111)


--dirk

Re: [POLL] What should happen to PyLucene now?

[Andi Vajda]

On Mon, 22 Aug 2016, Andi Vajda wrote:



On Sun, 10 Jul 2016, Andi Vajda wrote:


Thank you Jan for starting this thread !

Of the nine people that responded, three were interested in a new 6.x 
release, with two offering to help make a new release happen.


A couple of others showed interest in JCC only.

Here is what I can propose:
 1. I can make sure a PyLucene can be buildt from Lucene 6.x and runs.


PyLucene can now be built from Lucene's branch 6.x, on Mac OS X.
It builds, loads, can run a couple of simple tests like test_Binary.py and
test_BinaryDocument.py.

Here is how one can reproduce what I just did:
 - cd ~/apache
 - git clone --branch branch_6x https://github.com/apache/lucene-solr.git 
lucene.6x

 - cd 
 - svn update
   make sure you have a modern setuptools (if you are on linux, the
   setuptools patching done by JCC to be able to build a plain shared
   library most likely needs to be refreshed or maybe even eliminated).
 - _install/bin/pip uninstall setuptools
 - _install/bin/pip install setuptools
 - cd jcc
 - ../_install/bin/python setup.py build install
 - cd ..
 - make sources (this copies the lucene tree from the github tree cloned)
 - make compile install

If all worked, you can then:
 - _install/bin/python
 >>> import lucene
 >>> lucene.initVM()
 - _install/bin/python test/test_Binary.py

I have a Python virtual env installed in pylucene/_install, this helps with 
keeping different versions of software separate.



 2. Volunteers should then help in porting old 4.x tests, if they still
apply, and import new tests from the current Lucene suite as they see
fit.


All other tests need to be carefully ported to match all the numerous API 
changes and disappeared classes. For similar reasons, the extensions jar does 
not build and is not currently included in the build. Its source java classes 
need to be refreshed as tests get refreshed to 6.x.


PyLucene now builds and passes all its tests on Mac OS X and Linux.
It is thus in a state where a release candidate could be built and submitted 
for review.


A volunteer is requested to build and test PyLucene's trunk on Windows. If 
noone comes forward, I intend to try to release PyLucene 6.2 in a few weeks, 
still.


Thanks !

Andi..



Andi..


 3. Once everyone involved is happy with test coverage (which was never
exhaustive and need not be), a new release can be rolled and the
Lucene PMC put to contribution again for votes.

If any of these steps end up stalling, no new release happens and the 
PyLucene subproject gets shutdown, eventually.


As for JCC, regardless of what happens to PyLucene itself, I'd very much 
like to port it to Python 3. I've already done this once, the port is 
available in a branch [1]. It 'just' needs to be refreshed. I intend to 
eventually get to this, unless someone with a stronger itch beats me to it.


Andi..

[1] http://svn.apache.org/repos/asf/lucene/pylucene/branches/python_3/jcc/


On Sat, 2 Jul 2016, Aric Coady wrote:


[X]  I?ll help make a new release happen, if I get some help!

On Jul 1, 2016, at 9:35 AM, Alexander Yaworsky 
 wrote:


Well, this bothered me (not a dev but fixed some of your bugs locally
long long ago, why didn't send patches is another story). Here's my
opinion, as a user. 1. Be in sync with lucene is a must. 2. Be in sync
with python is a must. Therefore,


And +1 on staying current with lucene and python.


Question: What should happen to PyLucene now?

[ ]  I?m happy with the last 4.x release, no need for new releases
[ ]  Please, a new 6.x release (but I can?t contribute)
[ ]  I?ll help make a new release happen, if I get some help!
[X]  Only care about the JCC part
[X]  Close down the sub project -- IF YOU ARE UNABLE TO MAINTAIN
[ ]  Don?t care. I?m no longer a user
[X]  Other: Move JCC to P3


Actually, the brilliant part of this project is JCC. In a company I
work for we still use it to utilize Java libraries from python. This
is the fastest solution and this sub-project must exist separately
imo. We do not use Lucene since 00's btw.

Thanks.

Alexander.

Re: [POLL] What should happen to PyLucene now?

[Andi Vajda]

On Sun, 10 Jul 2016, Andi Vajda wrote:


Thank you Jan for starting this thread !

Of the nine people that responded, three were interested in a new 6.x 
release, with two offering to help make a new release happen.


A couple of others showed interest in JCC only.

Here is what I can propose:
 1. I can make sure a PyLucene can be buildt from Lucene 6.x and runs.


PyLucene can now be built from Lucene's branch 6.x, on Mac OS X.
It builds, loads, can run a couple of simple tests like test_Binary.py and
test_BinaryDocument.py.

Here is how one can reproduce what I just did:
  - cd ~/apache
  - git clone --branch branch_6x https://github.com/apache/lucene-solr.git 
lucene.6x
  - cd 
  - svn update
make sure you have a modern setuptools (if you are on linux, the
setuptools patching done by JCC to be able to build a plain shared
library most likely needs to be refreshed or maybe even eliminated).
  - _install/bin/pip uninstall setuptools
  - _install/bin/pip install setuptools
  - cd jcc
  - ../_install/bin/python setup.py build install
  - cd ..
  - make sources (this copies the lucene tree from the github tree cloned)
  - make compile install

If all worked, you can then:
  - _install/bin/python
  >>> import lucene
  >>> lucene.initVM()
  - _install/bin/python test/test_Binary.py

I have a Python virtual env installed in pylucene/_install, this helps with 
keeping different versions of software separate.



 2. Volunteers should then help in porting old 4.x tests, if they still
apply, and import new tests from the current Lucene suite as they see
fit.


All other tests need to be carefully ported to match all the numerous API 
changes and disappeared classes. For similar reasons, the extensions jar 
does not build and is not currently included in the build. Its source java 
classes need to be refreshed as tests get refreshed to 6.x.


Andi..


 3. Once everyone involved is happy with test coverage (which was never
exhaustive and need not be), a new release can be rolled and the
Lucene PMC put to contribution again for votes.

If any of these steps end up stalling, no new release happens and the 
PyLucene subproject gets shutdown, eventually.


As for JCC, regardless of what happens to PyLucene itself, I'd very much like 
to port it to Python 3. I've already done this once, the port is available in 
a branch [1]. It 'just' needs to be refreshed. I intend to eventually get to 
this, unless someone with a stronger itch beats me to it.


Andi..

[1] http://svn.apache.org/repos/asf/lucene/pylucene/branches/python_3/jcc/


On Sat, 2 Jul 2016, Aric Coady wrote:


[X]  I?ll help make a new release happen, if I get some help!

On Jul 1, 2016, at 9:35 AM, Alexander Yaworsky 
 wrote:


Well, this bothered me (not a dev but fixed some of your bugs locally
long long ago, why didn't send patches is another story). Here's my
opinion, as a user. 1. Be in sync with lucene is a must. 2. Be in sync
with python is a must. Therefore,


And +1 on staying current with lucene and python.


Question: What should happen to PyLucene now?

[ ]  I?m happy with the last 4.x release, no need for new releases
[ ]  Please, a new 6.x release (but I can?t contribute)
[ ]  I?ll help make a new release happen, if I get some help!
[X]  Only care about the JCC part
[X]  Close down the sub project -- IF YOU ARE UNABLE TO MAINTAIN
[ ]  Don?t care. I?m no longer a user
[X]  Other: Move JCC to P3


Actually, the brilliant part of this project is JCC. In a company I
work for we still use it to utilize Java libraries from python. This
is the fastest solution and this sub-project must exist separately
imo. We do not use Lucene since 00's btw.

Thanks.

Alexander.

Re: [POLL] What should happen to PyLucene now?

[Oliver Frietsch]

Hi,

(Sorry, just joined the list and so I'm unable to use a "real reply" in 
my mail client)


As for my company, our answers are:

[X] Still mostly happy with the 3.6 release, planning to upgrade to 4.x 
some time in future (please don't ask when, also requires a lot of 
changes in our product)...


[X] Have developed/updated Python3 Port of PyLucene3.6 and would be 
happy to contribute this


Please note: Two tests are still failing, seem to be some encoding issues.

[X] Please, a new 6.x release (but we can’t contribute and are uncertain 
if we'll upgrade soon)


Our PyLucene python 3 port is currently pushed forward by some 
"almost-retired" (but still having fun to code!) partner of us, so there 
is not too much manpower behind and not much more to expect in near 
future. But if that helps, we're very happy to contribute that existing 
patch.


Also, a huge thank you to all PyLucene committers so far! You did a 
great job!


Oliver

Re: [POLL] What should happen to PyLucene now?

[Andi Vajda]

Thank you Jan for starting this thread !

Of the nine people that responded, three were interested in a new 6.x 
release, with two offering to help make a new release happen.


A couple of others showed interest in JCC only.

Here is what I can propose:
  1. I can make sure a PyLucene can be buildt from Lucene 6.x and runs.
  2. Volunteers should then help in porting old 4.x tests, if they still
 apply, and import new tests from the current Lucene suite as they see
 fit.
  3. Once everyone involved is happy with test coverage (which was never
 exhaustive and need not be), a new release can be rolled and the
 Lucene PMC put to contribution again for votes.

If any of these steps end up stalling, no new release happens and the 
PyLucene subproject gets shutdown, eventually.


As for JCC, regardless of what happens to PyLucene itself, I'd very much 
like to port it to Python 3. I've already done this once, the port is 
available in a branch [1]. It 'just' needs to be refreshed. I intend to 
eventually get to this, unless someone with a stronger itch beats me to it.


Andi..

[1] http://svn.apache.org/repos/asf/lucene/pylucene/branches/python_3/jcc/


On Sat, 2 Jul 2016, Aric Coady wrote:


[X]  I?ll help make a new release happen, if I get some help!


On Jul 1, 2016, at 9:35 AM, Alexander Yaworsky  
wrote:

Well, this bothered me (not a dev but fixed some of your bugs locally
long long ago, why didn't send patches is another story). Here's my
opinion, as a user. 1. Be in sync with lucene is a must. 2. Be in sync
with python is a must. Therefore,


And +1 on staying current with lucene and python.


Question: What should happen to PyLucene now?

[ ]  I?m happy with the last 4.x release, no need for new releases
[ ]  Please, a new 6.x release (but I can?t contribute)
[ ]  I?ll help make a new release happen, if I get some help!
[X]  Only care about the JCC part
[X]  Close down the sub project -- IF YOU ARE UNABLE TO MAINTAIN
[ ]  Don?t care. I?m no longer a user
[X]  Other: Move JCC to P3


Actually, the brilliant part of this project is JCC. In a company I
work for we still use it to utilize Java libraries from python. This
is the fastest solution and this sub-project must exist separately
imo. We do not use Lucene since 00's btw.

Thanks.

Alexander.

Re: [POLL] What should happen to PyLucene now?

[Aric Coady]

[X]  I’ll help make a new release happen, if I get some help!

> On Jul 1, 2016, at 9:35 AM, Alexander Yaworsky  
> wrote:
> 
> Well, this bothered me (not a dev but fixed some of your bugs locally
> long long ago, why didn't send patches is another story). Here's my
> opinion, as a user. 1. Be in sync with lucene is a must. 2. Be in sync
> with python is a must. Therefore,

And +1 on staying current with lucene and python.

>> Question: What should happen to PyLucene now?
>> 
>> [ ]  I’m happy with the last 4.x release, no need for new releases
>> [ ]  Please, a new 6.x release (but I can’t contribute)
>> [ ]  I’ll help make a new release happen, if I get some help!
>> [X]  Only care about the JCC part
>> [X]  Close down the sub project -- IF YOU ARE UNABLE TO MAINTAIN
>> [ ]  Don’t care. I’m no longer a user
>> [X]  Other: Move JCC to P3
> 
> Actually, the brilliant part of this project is JCC. In a company I
> work for we still use it to utilize Java libraries from python. This
> is the fastest solution and this sub-project must exist separately
> imo. We do not use Lucene since 00's btw.
> 
> Thanks.
> 
> Alexander.

Re: [POLL] What should happen to PyLucene now?

[Petrus Hyvönen]

Hi,

I'm a user of JCC only. I would like to see a python-3 version but I do not
have the skills / time to do it myself unfortunately. I can help in testing.

I have looked at other alternative for JCC but none seems to provide the
integration such well, the "import" statement also is difficult in an
dynamic integration.

Many Thanks
/Petrus


On Fri, Jul 1, 2016 at 11:32 AM, Jan Høydahl  wrote:

> Hi
>
> As you all know not much has happened with PyLucene lately.
> So I’m throwing out this poll to check the sentiment of the community.
>
> Question: What should happen to PyLucene now?
>
> [ ]  I’m happy with the last 4.x release, no need for new releases
> [ ]  Please, a new 6.x release (but I can’t contribute)
> [ ]  I’ll help make a new release happen, if I get some help!
> [X]  Only care about the JCC part
> [ ]  Close down the sub project
> [ ]  Don’t care. I’m no longer a user
> [ ]  Other:
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
> Lucene commiter & PMC member




-- 
_
Petrus Hyvönen, Uppsala, Sweden
Mobile Phone/SMS:+46 73 803 19 00

Re: [POLL] What should happen to PyLucene now?

[Alexander Yaworsky]

No, it wouldn't.I haven't tried py4j, just looked at docs and the key
word I see is 'dynamic'. We used dynamic wrappers (I don't remember
exact names, that was too long ago, but the problem using JNI that way
is poor performance. JCC, in contrast, generates wrappers that provide
outstanding performance. This is what I love it for.

It's not a pain, I should say. Quite easy if you clearly understand
what it does :)

I would move it to P3 itself, but I have no enough time and P2 support
still gives 3.5 years for that :)

Alexander.

2016-07-01 23:42 GMT+07:00 Greg Bowyer :
> Would it make more sense to move to py4j like spark uses. JCC is awesome
> tech but installing it is a pain
>
> On Fri, Jul 1, 2016, at 09:35 AM, Alexander Yaworsky wrote:
>> Well, this bothered me (not a dev but fixed some of your bugs locally
>> long long ago, why didn't send patches is another story). Here's my
>> opinion, as a user. 1. Be in sync with lucene is a must. 2. Be in sync
>> with python is a must. Therefore,
>>
>> > Question: What should happen to PyLucene now?
>> >
>> > [ ]  I’m happy with the last 4.x release, no need for new releases
>> > [ ]  Please, a new 6.x release (but I can’t contribute)
>> > [ ]  I’ll help make a new release happen, if I get some help!
>> > [X]  Only care about the JCC part
>> > [X]  Close down the sub project -- IF YOU ARE UNABLE TO MAINTAIN
>> > [ ]  Don’t care. I’m no longer a user
>> > [X]  Other: Move JCC to P3
>>
>> Actually, the brilliant part of this project is JCC. In a company I
>> work for we still use it to utilize Java libraries from python. This
>> is the fastest solution and this sub-project must exist separately
>> imo. We do not use Lucene since 00's btw.
>>
>> Thanks.
>>
>> Alexander.

Re: [POLL] What should happen to PyLucene now?

[Greg Bowyer]

Would it make more sense to move to py4j like spark uses. JCC is awesome
tech but installing it is a pain

On Fri, Jul 1, 2016, at 09:35 AM, Alexander Yaworsky wrote:
> Well, this bothered me (not a dev but fixed some of your bugs locally
> long long ago, why didn't send patches is another story). Here's my
> opinion, as a user. 1. Be in sync with lucene is a must. 2. Be in sync
> with python is a must. Therefore,
> 
> > Question: What should happen to PyLucene now?
> >
> > [ ]  I’m happy with the last 4.x release, no need for new releases
> > [ ]  Please, a new 6.x release (but I can’t contribute)
> > [ ]  I’ll help make a new release happen, if I get some help!
> > [X]  Only care about the JCC part
> > [X]  Close down the sub project -- IF YOU ARE UNABLE TO MAINTAIN
> > [ ]  Don’t care. I’m no longer a user
> > [X]  Other: Move JCC to P3
> 
> Actually, the brilliant part of this project is JCC. In a company I
> work for we still use it to utilize Java libraries from python. This
> is the fastest solution and this sub-project must exist separately
> imo. We do not use Lucene since 00's btw.
> 
> Thanks.
> 
> Alexander.

Re: [POLL] What should happen to PyLucene now?

[Alexander Yaworsky]

Well, this bothered me (not a dev but fixed some of your bugs locally
long long ago, why didn't send patches is another story). Here's my
opinion, as a user. 1. Be in sync with lucene is a must. 2. Be in sync
with python is a must. Therefore,

> Question: What should happen to PyLucene now?
>
> [ ]  I’m happy with the last 4.x release, no need for new releases
> [ ]  Please, a new 6.x release (but I can’t contribute)
> [ ]  I’ll help make a new release happen, if I get some help!
> [X]  Only care about the JCC part
> [X]  Close down the sub project -- IF YOU ARE UNABLE TO MAINTAIN
> [ ]  Don’t care. I’m no longer a user
> [X]  Other: Move JCC to P3

Actually, the brilliant part of this project is JCC. In a company I
work for we still use it to utilize Java libraries from python. This
is the fastest solution and this sub-project must exist separately
imo. We do not use Lucene since 00's btw.

Thanks.

Alexander.

Re: [POLL] What should happen to PyLucene now?

[Jeff Breidenbach]

[x]  I’m happy with the last 4.x release, no need for new releases

With emphasis on the "happy" part. Not meant to be discouraging in any way.

Re: [POLL] What should happen to PyLucene now?

[Andi Vajda]

> On Jul 1, 2016, at 06:12, Joe Cabrera  wrote:
> 
> [X]  I’ll help make a new release happen, if I get some help!

The tests need porting :-)

Andi..

> 
>> On Fri, Jul 1, 2016 at 8:41 AM, Dirk Rothe  wrote:
>> 
>> Am 01.07.2016, 11:32 Uhr, schrieb Jan Høydahl :
>> 
>> Hi
>>> 
>>> As you all know not much has happened with PyLucene lately.
>>> So I’m throwing out this poll to check the sentiment of the community.
>>> 
>>> Question: What should happen to PyLucene now?
>> 
>> [X] Still mostly happy with the 3.6 release, pondering for at least 2
>> years whether to migrate to 4.x or elasticsearch.
>> 
>> And really grateful for the excellent job of Andi and the other
>> contributors. Thanx!
>> 
>> [ ]  I’m happy with the last 4.x release, no need for new releases
>>> [ ]  Please, a new 6.x release (but I can’t contribute)
>>> [ ]  I’ll help make a new release happen, if I get some help!
>>> [ ]  Only care about the JCC part
>>> [ ]  Close down the sub project
>>> [ ]  Don’t care. I’m no longer a user
>>> [ ]  Other: __
>>> 
>>> --
>>> Jan Høydahl, search solution architect
>>> Cominvent AS - www.cominvent.com
>>> Lucene commiter & PMC member
> 
> 
> -- 
> Joe Cabrera,
> eminorlabs.com

Re: [POLL] What should happen to PyLucene now?

[Marc Jeurissen]

On 1/07/2016 11:32, Jan Høydahl wrote:

Hi

As you all know not much has happened with PyLucene lately.
So I’m throwing out this poll to check the sentiment of the community.

Question: What should happen to PyLucene now?

[ ]  I’m happy with the last 4.x release, no need for new releases
[X]  Please, a new 6.x release (but I can’t contribute)
[ ]  I’ll help make a new release happen, if I get some help!
[ ]  Only care about the JCC part
[ ]  Close down the sub project
[ ]  Don’t care. I’m no longer a user
[ ]  Other: __

--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
Lucene commiter & PMC member


--
Signature Marc Jeurissen | UAntwerpen
Met vriendelijke groeten,

Marc Jeurissen


Bibliotheek UAntwerpen
Stadscampus - S.A.085
Prinsstraat 9 - 2000 Antwerpen
marc.jeuris...@uantwerpen.be 
T +32 3 265 49 71

Re: [POLL] What should happen to PyLucene now?

[Joe Cabrera]

[X]  I’ll help make a new release happen, if I get some help!

On Fri, Jul 1, 2016 at 8:41 AM, Dirk Rothe  wrote:

> Am 01.07.2016, 11:32 Uhr, schrieb Jan Høydahl :
>
> Hi
>>
>> As you all know not much has happened with PyLucene lately.
>> So I’m throwing out this poll to check the sentiment of the community.
>>
>> Question: What should happen to PyLucene now?
>>
>
> [X] Still mostly happy with the 3.6 release, pondering for at least 2
> years whether to migrate to 4.x or elasticsearch.
>
> And really grateful for the excellent job of Andi and the other
> contributors. Thanx!
>
> [ ]  I’m happy with the last 4.x release, no need for new releases
>> [ ]  Please, a new 6.x release (but I can’t contribute)
>> [ ]  I’ll help make a new release happen, if I get some help!
>> [ ]  Only care about the JCC part
>> [ ]  Close down the sub project
>> [ ]  Don’t care. I’m no longer a user
>> [ ]  Other: __
>>
>> --
>> Jan Høydahl, search solution architect
>> Cominvent AS - www.cominvent.com
>> Lucene commiter & PMC member
>>
>


-- 
Joe Cabrera,
eminorlabs.com

Re: [POLL] What should happen to PyLucene now?

[Dirk Rothe]

Am 01.07.2016, 11:32 Uhr, schrieb Jan Høydahl :


Hi

As you all know not much has happened with PyLucene lately.
So I’m throwing out this poll to check the sentiment of the community.

Question: What should happen to PyLucene now?


[X] Still mostly happy with the 3.6 release, pondering for at least 2  
years whether to migrate to 4.x or elasticsearch.


And really grateful for the excellent job of Andi and the other  
contributors. Thanx!



[ ]  I’m happy with the last 4.x release, no need for new releases
[ ]  Please, a new 6.x release (but I can’t contribute)
[ ]  I’ll help make a new release happen, if I get some help!
[ ]  Only care about the JCC part
[ ]  Close down the sub project
[ ]  Don’t care. I’m no longer a user
[ ]  Other: __

--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
Lucene commiter & PMC member

RE: [POLL] What should happen to PyLucene now?

[Mark Csaba]

Hello :)

-Original Message-
From: Jan Høydahl [mailto:jan@cominvent.com] 
Sent: Friday, July 01, 2016 11:32 AM
To: pylucene-dev@lucene.apache.org
Subject: [POLL] What should happen to PyLucene now?

Hi

As you all know not much has happened with PyLucene lately.
So I’m throwing out this poll to check the sentiment of the community.

Question: What should happen to PyLucene now?

[ ]  I’m happy with the last 4.x release, no need for new releases 

[X]  Please, a new 6.x release (but I can’t contribute) 

[ ]  I’ll help make a new release happen, if I get some help!
[ ]  Only care about the JCC part
[ ]  Close down the sub project
[ ]  Don’t care. I’m no longer a user
[ ]  Other: __

--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
Lucene commiter & PMC member