Re: [rdf4j-dev] Solr and Elastic Search

[Jeen Broekstra <jeen.broekstra@xxxxxxxxx>]

Well, don't forget that many people may be using it through maven. I'm pretty sure Marc himself uses these backends, and there have been several stack overflow and mailing list questions about them. Also they haven't been around that long, and I think they're a nice proposition: we give people a choice of text indexing tool, something few other frameworks do I think.

Is there a particular reason you want to get rid of them?

Cheers,

Jeen

On 28 Jul. 2017 10:28 pm, "James Leigh" <james.leigh@xxxxxxxxxxxx> wrote:

On Thu, 2017-07-27 at 08:53 +1000, Jeen Broekstra wrote:
>
> > On 27 Jul 2017, at 02:47, James Leigh <james.leigh@xxxxxxxxxxxx>
> > wrote:
> > Should we deprecate these? Or, have we already?
> They’re not deprecated AFAIK. They’re also still documented as viable
> backends for the search index implementation (see http://docs.rdf4j.o
> rg/programming/#_searchindex_implementations). 
>
> I’m not sure why they’d be left out of the onejar/sdk, though. I
> remember we did a bit of juggling with module renaming and moves at
> the time, and we did deprecate other implementations (Lucene 3 and
> 4). I think we also had some questions around IP for
> Solr/Elasticsearch when transferring the project to Eclipse.

I propose we deprecate them in the next patch release and remove them
altogether in the next minor release. If no body has noticed their
absents in the last two year, then I think we can assume they are not
adding any value to the project.

James
_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rdf4j-dev