[ https://issues.apache.org/jira/browse/SOLR-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15080548#comment-15080548 ]
Jason Gerlowski commented on SOLR-7535: --------------------------------------- Haha, I take it that the manual testing didn't go well then. I like the local-buffering idea. Out of curiosity, do you think there'd be any value in making the different behaviors entirely different TupleStream implementations (i.e. {{update()}} and {{buffered-update()}}). It might make the calling syntax a little easier (one less parameter). And it might keep the code cleaner, if we can avoid a bunch of {{if (buffered)...else...}} clauses. Just a thought. I'm fine w/ having this be param controlled too. > Add UpdateStream to Streaming API and Streaming Expression > ---------------------------------------------------------- > > Key: SOLR-7535 > URL: https://issues.apache.org/jira/browse/SOLR-7535 > Project: Solr > Issue Type: New Feature > Components: clients - java, SolrJ > Reporter: Joel Bernstein > Assignee: Joel Bernstein > Priority: Minor > Attachments: SOLR-7535.patch, SOLR-7535.patch, SOLR-7535.patch, > SOLR-7535.patch, SOLR-7535.patch, SOLR-7535.patch > > > The ticket adds an UpdateStream implementation to the Streaming API and > streaming expressions. The UpdateStream will wrap a TupleStream and send the > Tuples it reads to a SolrCloud collection to be indexed. > This will allow users to pull data from different Solr Cloud collections, > merge and transform the streams and send the transformed data to another Solr > Cloud collection. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org