[
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
[
https://issues.apache.org/jira/browse/PYLUCENE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445964#comment-17445964
]
David Allouche commented on PYLUCENE-52:
Apply this patch to compile lu
> 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 integr
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 que
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 t
ucene 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.
>>
>> O
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, conf
