epugh commented on PR #3670:
URL: https://github.com/apache/solr/pull/3670#issuecomment-3328551433

   I had a thought late last night @janhoy...    So while I am super excited 
about the pluggable idea, I wonder if we have lost the core goal?   The core 
goal is _to offer a way of reading rich documents for indexing in Solr without 
the maintenance burden on Solr and to be more in line with future of Tika_.   
If that is the core goal, I wonder if we should just target TikaServer in Solr 
10, and not worry about any backcompat, beyond documenting it etc.   We should 
just embrace the new ways of Tika working.  If that makes sense, maybe the fact 
that some capabilities in Solr don't work at this point, like passwords or 
xpath, is okay if it's a Solr 10 only thing?   
   
   Does saying this is a Solr 10 only thing make it easier to have the tests 
pass by tweaking them  and our implementation to leverage how Tika 3 and 
TikaServer works?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to