> > > > > *That's not usually the kind of information you want to have in a > Solrindex. Most of the time, there will be an entry in the Solr index > thattells the system making queries how to locate the actual data -- > afilename, a URL, a database lookup key, etc.*
Agreed. The app will have a few implementations for storing the binary file. Easiest for a user to configure for proto-typing would be store in index impl. A live impl would probably be fs *We don't recommend using solr-cell for production indexing.* Ok. Are the reasons for: Performance. I think we have rather modest index requirement (1000 a day... on a busy day) Security. The index workflow is, upload files to public facing server with auth. Files written to disk, scanned and copied to internal server and ingested into index via here. other reasons we should worry about ? Cheers Lee C On 25 April 2018 at 00:37, Shawn Heisey <apa...@elyograg.org> wrote: > On 4/24/2018 10:26 AM, Lee Carroll wrote: > > Does the solr cell contrib give access to the files raw content along > with > > the extracted metadata?\ > > That's not usually the kind of information you want to have in a Solr > index. Most of the time, there will be an entry in the Solr index that > tells the system making queries how to locate the actual data -- a > filename, a URL, a database lookup key, etc. > > I have no idea whether solr-cell can put the info in the index. My best > guess would be that it can't, since putting the entire binary content > into the index isn't recommended. > > We don't recommend using solr-cell for production indexing. If you > follow recommendations and write your own indexing program using Tika, > then you can do pretty much anything you want, including writing the > full content into the index. > > Thanks, > Shawn > >
