sorry thought I was on UIMA mailing list. That being said, my position is the same :
let UIMA folks load data into SolR by using the most optimized way. (what would be the best way ? Loading jsons ?) 2018-06-19 22:48 GMT+02:00 Nicolas Paris <nipari...@gmail.com>: > Hi > > Not realy a direct answer - Never used it, however this feature have > been attractive to me while first looking at uima. > > Right now, I would say UIMA connectors in general are by design > a pain to maintain. Source and target often do have optimised > way to bulk export/import data. For example, using a jdbc postgresql > connector is a bad idea compared to using the optimzed COPY function. > And each database has it's own optimized way of doing. > > That's why developpers of UIMA should focus on improving what UIMA > is good at: processing texts. > Exporting and importing texts responsibility should remain to the other > tools. > > Tell me if i am wrong > > 2018-06-18 13:13 GMT+02:00 Alexandre Rafalovitch <arafa...@gmail.com>: > >> Hi, >> >> Solr ships an UIMA component and examples that haven't worked for a >> while. Details are in: >> https://issues.apache.org/jira/browse/SOLR-11694 >> >> The choices for developers are: >> 1) Rip UIMA out (and save space) >> 2) Update UIMA to latest 2.x version >> 3) Update UIMA to super-latest possibly-breaking 3.x >> >> The most likely choice at this point is 1. But I am curious (given >> that UIMA is in IBM Watson...) if anybody actually has a use-case that >> strongly votes for options 2 or 3, given that the update effort is >> probably not trivial. >> >> Note that if you use UIMA with Solr, but in a configuration completely >> different from that shipped (so the options 2/3 would still be >> irrelevant), it could be still fun to share the knowledge in this >> thread, with the appropriate disclaimer. >> >> Regards, >> Alex. >> > >
