+1 to the plan, and sorry to have been out of touch for several days. It turns
out that Osma and I are at the same workshop but have only had a few minutes to
talk!
I think we will want to include some notes for the release about how to
configure Fuseki2 to use ES. Or perhaps that should just go in the ES module?
I agree that exclusions are much harder to reason about than keeping a kind of
"partial order" in dependency.
ajs6f
Andy Seaborne wrote on 4/25/17 6:52 AM:
How does this sound as the route to 3.3.0?
Merge these PRs (which I think are all ready to go):
PR#245 :: Maven module for ElasticSearch, not in Fuseki2 in 3.3.0
PR#243 :: JENA-1324: Check for spaces in URIs (if RDF 1.1)
PR#242 :: JENA-1323: RDFWriter
PR#244 :: Open iterators when cancelling a query during sorting
and close PR#240, an alternative to PR#241 which is in the code now.
Please +1, or comment otherwise, and if it seems like a plan, I'll go ahead and
do these items.
Andy
PR#245 - stops the Fuseki server going from 25M to 70M. We can decide later if
we want ES in Fuseki - it's easier to add later, then ship now then remove.
There are other ways to not end up with the ES dependencies such as exclusions.
I prefer a module structure to using exclusions to pick and choose what goes
into Fuseki.
