lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] Commented: (SOLR-1526) Client Side Tika integration
Date Wed, 22 Dec 2010 12:51:02 GMT


Jan Høydahl commented on SOLR-1526:

I linked this issue to SOLR-1763, as they attempt to solve the same thing, on client vs server

Instead of creating two solutions, we should base these two on same code base and config,
so that it is easy to switch between them. Perhaps someone starts with server-side extraction
but then want to optimize performance by going client-side. The switch should be intuitive.

Thus, should we consider porting the whole UpdateProcessorChain to SolrJ? How cool would it
be to choose whether to execute an UP on client or server side simply by configuration change?
I realize that some UP's may depend on SolrCore or have other difficult dependencies, but
it should be possible to work around, not?

> Client Side Tika integration
> ----------------------------
>                 Key: SOLR-1526
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: clients - java
>            Reporter: Grant Ingersoll
>            Priority: Minor
>             Fix For: Next
> Often times it is cost prohibitive to send full, rich documents over the wire.  The contrib/extraction
library has server side integration with Tika, but it would be nice to have a client side
implementation as well.  It should support both metadata and content or just metadata.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message