Closed GoogleCodeExporter closed 9 years ago
There are plans but no schedules - see
https://code.google.com/p/semanticvectors/wiki/LuceneCompatibility.
We can use this thread to prioritize, though - is this urgent / blocking for
you?
Original comment by dwidd...@gmail.com
on 15 Jun 2013 at 3:40
It would be really great to have it, as currently I'm maintaining two different
Lucene indexes (indexed individually) in two separate processes in order to
integrate the functionality of Semantic Vectors with the usual Lucene
functionality. I could, obviously, revert back to using only Lucene 3.6,
however I thought I'd ask first about your plans to port it to 4.x.x.
Bottom line - it would help me greatly, but it is, obviously, not urgent.
Thank you.
Original comment by tudor.gr...@gmail.com
on 15 Jun 2013 at 10:39
I hear ya ... and I imagine this situation is going to become more common the
more we procrastinate. I will try to look at this during the coming week or two
at most. -Dominic
Original comment by dwidd...@gmail.com
on 17 Jun 2013 at 6:29
As of revision 931, code for integrating with Lucene 4.3 is checked into trunk
https://code.google.com/p/semanticvectors/source/detail?r=931
We'll allow a few days for testing and then release.
Original comment by dwidd...@gmail.com
on 6 Jul 2013 at 12:29
Works like a charm! Thank you!
Original comment by tudor.gr...@gmail.com
on 7 Aug 2013 at 6:32
Great - marking as fixed and verified. Thanks for the feedback!
Original comment by dwidd...@gmail.com
on 7 Aug 2013 at 4:02
Issue 63 has been merged into this issue.
Original comment by dwidd...@gmail.com
on 7 Aug 2013 at 4:03
Original issue reported on code.google.com by
tudor.gr...@gmail.com
on 14 Jun 2013 at 11:03