Eric24
Jun 8, 2016, 11:15:30 PM6/8/16
to OrientDB
What version of Lucene is currently supported in OrientDB 2.2.0? If less than 6.0, what would be required to support 6.0/6.0.1 (and/or if and when is this on the road map)? If 6.0 or later, are 3D/nD spatial indexes supported? For example, there is no enforced limit on the number of elements that can be stored in an OPoint, so technically it should be possible to store a 3D (or nD) point, but are the various internal functions (ST_*) and/or the interface to Lucene able to support this for indexing/querying?
--Eric
scott molinari
Jun 9, 2016, 1:26:14 AM6/9/16
to OrientDB
If I read the code/ config in the Lucene index section of ODB, it looks like it is using 4.7.0, which is disappointing, considering the Lucene team is working on version 7.
Roberto Franchini
Jun 9, 2016, 2:40:36 AM6/9/16
to orient-...@googlegroups.com
On Thu, Jun 9, 2016 at 7:26 AM, 'scott molinari' via OrientDB <orient-...@googlegroups.com> wrote:
If I read the code/ config in the Lucene index section of ODB, it looks like it is using 4.7.0, which is disappointing, considering the Lucene team is working on version 7.
Hi,
on 2.2.0 we use Lucene we are on 5.3.2
moving to 5.5 or better to 6.x is planned for 3.x.
Note that Lucene has changed some internals (e.g.: non more filters, only queries) and we need to refactor/rewrite and TEST deeply the code .
Eric Lenington
Jun 9, 2016, 9:22:35 AM6/9/16
to OrientDB
Thanks Roberto. This isn't a current need for us (2D point-mapping is fine for now), but it is important for our database architecture. On that point (no pun intended), do you see any reason why OPoint and related Geo objects wouldn't just be "extended" to handle 3D, 4D, nD points in the future by simple setting more items in the array?
--
---
You received this message because you are subscribed to a topic in the Google Groups "OrientDB" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/orient-database/6S609dE548I/unsubscribe.
To unsubscribe from this group and all its topics, send an email to orient-databa...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Roberto Franchini
Jun 9, 2016, 10:30:26 AM6/9/16
to orient-...@googlegroups.com
On Thu, Jun 9, 2016 at 3:22 PM, Eric Lenington <er...@24x8.com> wrote:
Thanks Roberto. This isn't a current need for us (2D point-mapping is fine for now), but it is important for our database architecture. On that point (no pun intended), do you see any reason why OPoint and related Geo objects wouldn't just be "extended" to handle 3D, 4D, nD points in the future by simple setting more items in the array?
We will explore for 3.0 3d and new lucene 6 points features.
scott molinari
Jun 9, 2016, 10:43:36 AM6/9/16
to OrientDB
Hey Roberto.
Off-topic, but when do you all update the master branch? I would have assumed the master branch is at the same level as the last release (and why my reply was wrong).
Scott
Off-topic, but when do you all update the master branch? I would have assumed the master branch is at the same level as the last release (and why my reply was wrong).
Scott
Roberto Franchini
Jun 9, 2016, 12:21:55 PM6/9/16
to orient-...@googlegroups.com
On Thu, Jun 9, 2016 at 4:43 PM, 'scott molinari' via OrientDB <orient-...@googlegroups.com> wrote:
Hey Roberto.
Off-topic, but when do you all update the master branch? I would have assumed the master branch is at the same level as the last release (and why my reply was wrong).
Master should contains the latests stable release.
But now we are on 2.2, and I've not merged yet, leaving tags on the develop branch and for 2.1.19 on 2.1.x:
So your answer was not so wrong :)
Stay tuned, I'll fix github in a few days.
Reply all
Reply to author
Forward
0 new messages