[
https://issues.apache.org/jira/browse/SOLR-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978825#action_12978825
]
Tomás Fernández Löbbe commented on SOLR-1526:
---------------------------------------------
Now I get what you say about the UpdateRequestProcessor (I thought you where
talking about a different/new component). I like the idea of reuse the code, I
don't like the idea of adding complexity to SolrJ. Is it worthy to port the
UpadateRequestProcessorChain to SolrJ? I definitely wouldn't like to have a
configuration file on the SolrJ API.
> Client Side Tika integration
> ----------------------------
>
> Key: SOLR-1526
> URL: https://issues.apache.org/jira/browse/SOLR-1526
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
