Hi Joel,
Thanks for confirming that Streaming would be too costly for high qps loads.
Regards,
--
View this message in context:
http://lucene.472066.n3.nabble.com/Using-of-Streaming-to-join-between-shards-tp4342563p4343104.html
Sent from the Solr - User mailing list archive at Nabble.com.
I don't think the distributed joins are going to work for you in the ACL
use case you describe. I think the overhead of streaming the documents will
be too costly in this scenario. The distributed joins were designed more
for OLAP data warehousing use cases rather then high QPS loads.
Joel
Hi Susheel,
Thanks for your reply and as you suggested we will start with innerJoin.
But what I want know is that, Is Streaming can be used instead of normal
default Join ?
For ex. currently we fire request for every user clicks on menu in the page
to show list of his documents with default
You may want to start with innerJoin which is the simple typical join in
database world.
On Mon, Jun 26, 2017 at 1:46 AM, mganeshs wrote:
> Hi Erick,
>
> My scenario goes with two kind of SOLR documents
>
> Document #1 - Real document
> #D_uniqueId #D_documentId(unique),
Hi Erick,
My scenario goes with two kind of SOLR documents
Document #1 - Real document
#D_uniqueId #D_documentId(unique), #D_documentname, #D_documentdesc,
#D_documentinfo1, #D_documentInfo2, #D_documentInfo3, ...
Document #2 - to hold documents ACL
#P_uniqueId #P_acl_perm ( multi value field,
You've provided no information to help guide an answer and even with
more information there are too many variables to say definitively.
There are quite a number of Streaming join options, see:
https://cwiki.apache.org/confluence/display/solr/Streaming+Expressions.
You'll have to do some