It works well. Thanks. On 24 December 2014 at 12:01, Andi Vajda <va...@apache.org> wrote:
> > On Wed, 24 Dec 2014, iceout wrote: > > I just subscribe the mail list. And I don't know how reply the thread >> before. So I have to create a new one. >> >> In lucene 4.4, the method newTermQuery() is defined in class >> QueryParserBase, and QueryParser extends QueryParserBase. >> >> In lucene 4.10, the method newTermQuery() is defined in class >> QueryBuilder, >> and class QueryParserBase extends QueryBuilder, and class QueryParser >> extends QueryParserBase. >> >> In java, I can simply override newTermQuery() method when extends >> QueryParser. >> But in pylucene, it didn't work, both 4.4 and 4.10 version. >> >> Is there something wrong? >> > > If you apply the attached patch to a PyLycene 4.10.1 checkout: > (if the attachment disappeared, let me know and I'll send it inline) > $ cd <PyLucene 4.10.1 source directory> > $ patch -Nup0 < patch.newTermQuery.txt > and rebuild PyLucene > $ find . -name 'extensions.jar' | xargs rm > $ make > and run tests > $ make test > you should see that newTermQuery is called when the > test_PythonQueryParser.py > file is run by make test, that this output is emitted: > .CALLING newTermQuery with all:foo > CALLING newTermQuery with all:bar > . > > As far as stock 4.10.1 PyLucene is concerned, extended newTermQuery() as > shown by this patch seems to be working as expected. > If you find otherwise, please reply with a patch that applies to PyLucene > 4.10.1, that reproduces the problem you're experiencing. > > Thanks ! > > Andi.. > > >> -- >> Best Regards, >> iceout >> > -- Best Regards, iceout
