Re: Is it possible to index documents without storing their content?

Thanks Emir for the great answer :) Br Tom 2018-05-23 10:16 GMT+02:00 Emir Arnautović : > Hi Tom, > Yes it is possible - see field options: https://lucene.apache.org/ > solr/guide/6_6/defining-fields.html#DefiningFields- > OptionalFieldTypeOverrideProperties solr/g

Re: Is it possible to index documents without storing their content?

Hi Tom, Yes it is possible - see field options: https://lucene.apache.org/solr/guide/6_6/defining-fields.html#DefiningFields-OptionalFieldTypeOverrideProperties . There is stored op

Re: is it possible to index

Do note that you _can_ join across cores. BUT the join capability is a fairly restricted use-case. And even if it was performant, it's not like a DB join, you can only return info from a single kind of doc. That is, if you were joining between customer documents and vendor documents, you could only

Re: is it possible to index

This is gold info for me! Thanks! 2012/10/24 Martin Koch > In my experience, about as fast as you can push the new data :) Depending > on the size of your records, this should be a matter of seconds. > > /Martin Koch > > On Wed, Oct 24, 2012 at 9:01 PM, Marcelo Elias Del Valle < > mvall...@gmail

Re: is it possible to index

In my experience, about as fast as you can push the new data :) Depending on the size of your records, this should be a matter of seconds. /Martin Koch On Wed, Oct 24, 2012 at 9:01 PM, Marcelo Elias Del Valle wrote: > Erick, > > Thanks for the help, it sure helps a lot to read that, as it

Re: is it possible to index

Erick, Thanks for the help, it sure helps a lot to read that, as it gives me more confidence I am not crazy about what I am thinking. The only problem I see by de-normalizing data as you said is that if any relation between customer and vendor changes, I will have to update the index for

Re: is it possible to index

One, take off your RDBMS cap ... DB folks regularly reject the idea of de-normalizing data to make best use of Solr, but that's what I would explore first. Yes, this repeats the, in your case, vendor information perhaps many times, but try that first, even though that causes you to update multiple