[
https://issues.apache.org/jira/browse/SOLR-8556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-8556:
---------------------------------
Description:
Now that we have the UpdateStream it would be nice to support the use case of
sending rolled up aggregates for storage in another SolrCloud collection. To
support this we'll need to create id's for the aggregate records.
The ConcatOperation would allows us to concatenate the bucket values into a
unique id. For example:
{code}
update(
select(
rollup(search(q="*:*, fl="a,b,c", ...)),
concat(fields="a,b,c", delim="_", as="id")))
{code}
was:
Now that we have the UpdateStream it would be nice to support the use case of
sending rolled up aggregates for storage in another SolrCloud collection. To
support this we'll need to create id's for the aggregate records.
The ConcatOperation would allows us to concatenate the bucket values into a
unique id. For example:
{code}
update(
select(
rollup(search()),
concat(fields="a,b,c", delim="_", as="id")))
{code}
> Add ConcatOperation to be used with the SelectStream
> ----------------------------------------------------
>
> Key: SOLR-8556
> URL: https://issues.apache.org/jira/browse/SOLR-8556
> Project: Solr
> Issue Type: New Feature
> Reporter: Joel Bernstein
>
> Now that we have the UpdateStream it would be nice to support the use case of
> sending rolled up aggregates for storage in another SolrCloud collection. To
> support this we'll need to create id's for the aggregate records.
> The ConcatOperation would allows us to concatenate the bucket values into a
> unique id. For example:
> {code}
> update(
> select(
> rollup(search(q="*:*, fl="a,b,c", ...)),
> concat(fields="a,b,c", delim="_", as="id")))
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
