Hi Chris, Responding on dev list for a wider audience if that's OK.
I looked a bit at jena-spatial, and it has the same issues with transactions that the TextIndexLucene in jena-text previously had. Basically it is not managing the transaction boundaries properly. Additionally, jena-spatial is based on Lucene as well. There is a ton of duplicated code between the two projects. I would suggest either combining both projects into a single project or adding a common dependency that they can both use. That way we can get rid of all the duplicate code and have a single place dealing with Lucene transaction logic. Use the jena-text transaction logic and ignore the transaction logic in jena-spatial when combining. I would recommend the first option of combining them into a single project (maybe jena-external-index or something like that). I think this route might be better because I can imagine other types of indexes that we would like to add, such as a temporal index (although since that is scalar (for the most part), maybe it could be done directly in TDB instead of an external index, since the B-Trees store things sorted). -Stephen On Fri, May 8, 2015 at 10:50 AM, Chris Dollin <[email protected]> wrote: > Hi Stephen > > I'd like to lean on your expertise if I may. We're hoping > to use jena-spatial for geo-queries in some work, > but we know that it has not had its transaction-handling > updated. I'll be reviewing it (after this coming weeks > holiday YAY) to see if that will cause us any problems. > > Any tips or documentation you have would be valuable; > I see there are some details in JENA-848 for jena-text > but if there's useful discussion elsewhere that would > be handy. Especially if there's a NO DON'T DO THAT we > should know about. > > Chris > > > > > > > >
