lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SOLR-9562) Minimize queried collections for time series alias
Date Mon, 14 Aug 2017 10:48:00 GMT

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

Jan Høydahl commented on SOLR-9562:
-----------------------------------

bq. what is the methodology to reducing the numShards of a collection while keeping overall
data set searchable and no oddities like temporarily searching/counting copies of the same
document? And likewise for merging collections?

I wish I had all the answers :) Regarding reduce shards, perhaps a pure merge would be simplest,
i.e. if you have 6 shards to tackle high indexing rate and NRT, then the API would support
a reduce to 3 shards. Reducing to some other number would be harder and likely require re-indexing
(streaming) all docs into a new shadow collection? The same could be done for merging collections
- stream all docs from collection 1 and 2 into new collection 3.

> Minimize queried collections for time series alias
> --------------------------------------------------
>
>                 Key: SOLR-9562
>                 URL: https://issues.apache.org/jira/browse/SOLR-9562
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Eungsop Yoo
>            Priority: Minor
>         Attachments: SOLR-9562.patch, SOLR-9562-v2.patch
>
>
> For indexing time series data(such as large log data), we can create a new collection
regularly(hourly, daily, etc.) with a write alias and create a read alias for all of those
collections. But all of the collections of the read alias are queried even if we search over
very narrow time window. In this case, the docs to be queried may be stored in very small
portion of collections. So we don't need to do that.
> I suggest this patch for read alias to minimize queried collections. Three parameters
for CREATEALIAS action are added.
> || Key || Type || Required || Default || Description ||
> | timeField | string | No | | The time field name for time series data. It should be
date type. |
> | dateTimeFormat | string | No | | The format of timestamp for collection creation. Every
collection should has a suffix(start with "_") with this format. 
> Ex. dateTimeFormat: yyyyMMdd, collectionName: col_20160927
> See [DateTimeFormatter|https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html].
|
> | timeZone | string | No | | The time zone information for dateTimeFormat parameter.
> Ex. GMT+9. 
> See [DateTimeFormatter|https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html].
|
> And then when we query with filter query like this "timeField:\[fromTime TO toTime\]",
only the collections have the docs for a given time range will be queried.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message