[
https://issues.apache.org/jira/browse/SOLR-11722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278751#comment-16278751
]
David Smiley commented on SOLR-11722:
-------------------------------------
I can see the value in an "example collection" but I think this requires the
user to do more in most cases. They have to create this dummy collection 1st,
which obviates some of the convenience we're trying to offer. This dummy
collection might take up resources (e.g. cores on some nodes) that will prevent
choosing some nodes for future replica allocations. If you want to add this as
a convenience option then it seems fine to me, but not mandatory. If you want
to keep it, I suggest the name "template collection" rather than "example".
RE timezones: It'd be nice to call it "TZ" to be consistent with use of it
elsewhere. But not a big deal. I think the choice of how collection names are
to be formatted here took place in SOLR-11542 to be released in Solr 7.2
shortly. I agree we don't want the user to read the code to know such things;
so at the very least we should document. The docs on this timezone param
should spell this out.
By the way, notice how the create-collection command has a "router" _property_
that itself has sub-properites of "name" and "field". That's interesting.
[~noble.paul] how does one express that as an API command? It's not clear
reading
https://builds.apache.org/job/Solr-reference-guide-master/javadoc/v2-api.html
which is what I've been using as the docs on this V2 API. [~noble.paul] are we
required to document each parameter or can we say that properties starting with
"createCollection." are mapped to collection creation parameters?
> API to create a Time Routed Alias and first collection
> ------------------------------------------------------
>
> Key: SOLR-11722
> URL: https://issues.apache.org/jira/browse/SOLR-11722
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: David Smiley
>
> This issue is about creating a single API command to create a "Time Routed
> Alias" along with its first collection. Need to decide what endpoint URL it
> is and parameters.
> Perhaps in v2 it'd be {{/api/collections?command=create-routed-alias}} or
> alternatively piggy-back off of command=create-alias but we add more options,
> perhaps with a prefix like "router"?
> Inputs:
> * alias name
> * misc collection creation metadata (e.g. config, numShards, ...) perhaps in
> this context with a prefix like "collection."
> * metadata for TimeRoutedAliasUpdateProcessor, currently: router.field
> * date specifier for first collection; can include "date math".
> We'll certainly add more options as future features unfold.
> I believe the collection needs to be created first (referring to the alias
> name via a core property), and then the alias pointing to it which demands
> collections exist first. When figuring the collection name, you'll need to
> reference the format in TimeRoutedAliasUpdateProcessor.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
