lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joel Bernstein (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-6526) Solr Streaming API
Date Wed, 17 Sep 2014 15:17:35 GMT

    [ https://issues.apache.org/jira/browse/SOLR-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137372#comment-14137372
] 

Joel Bernstein edited comment on SOLR-6526 at 9/17/14 3:17 PM:
---------------------------------------------------------------

The /export handler doesn't mesh with the full range of Solr features. It wasn't designed
to because it was built to support specific non-traditional search use cases. For example
you can't change the response writer with it or output facets. So it really is a different
animal, having it's own request handler makes that clear. 

But the use cases that it does support are extremely important. And having this feature available
makes Solr much more powerful.








was (Author: joel.bernstein):
The /export handler doesn't mesh with the full range of Solr features. It wasn't designed
to because it was built to support specific non-traditional search use case. For example you
can't change the response writer with it or output facets. So it really is a different animal,
having it's own request handler makes that clear. 

But the use cases that it does support are extremely important. And having this feature available
makes Solr much more powerful.







> Solr Streaming API
> ------------------
>
>                 Key: SOLR-6526
>                 URL: https://issues.apache.org/jira/browse/SOLR-6526
>             Project: Solr
>          Issue Type: New Feature
>          Components: clients - java
>            Reporter: Joel Bernstein
>             Fix For: 5.0
>
>         Attachments: SOLR-6526.patch
>
>
> It would be great if there was a SolrJ library that could connect to Solr's /export handler
(SOLR-5244) and perform streaming operations on the sorted result sets.
> This ticket defines the base interfaces and implementations for the Streaming API. The
base API contains three classes:
> *SolrStream*: This represents a stream from a single Solr instance. It speaks directly
to the /export handler and provides methods to read() Tuples and close() the stream
> *CloudSolrStream*: This represents a stream from a SolrCloud collection. It speaks with
Zk to discover the Solr instances in the collection and then creates SolrStreams to make the
requests. The results from the underlying streams are merged inline to produce a single sorted
stream of tuples.
> *Tuple*: The data structure returned by the read() method of the SolrStream API. It is
nested to support grouping and Cartesian product set operations.
> Once these base classes are implemented it paves the way for building *Decorator* streams
that perform operations on the sorted Tuple sets. For example a CollapseStream could be created:
> {code}
> CollapseStream collapseStream = new CollapseStream(new CloudSolrStream(zkUrl, queryRequest));
> Tuple tuple = null;
> while((tuple = collapseStream.read()) != null) {
> } 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message