[jira] [Commented] (SOLR-5955) Add config templates to SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14609427#comment-14609427 ] Gregory Chanan commented on SOLR-5955: -- I posted an initial patch for the immutable part of config sets in SOLR-7742. I think this jira is still relevant as a separate jira because it is tackling related issues (e.g. creating a collection in one step from a config template). > Add config templates to SolrCloud. > -- > > Key: SOLR-5955 > URL: https://issues.apache.org/jira/browse/SOLR-5955 > Project: Solr > Issue Type: New Feature >Reporter: Mark Miller > Attachments: SOLR-5955.patch > > > You should be able to upload config sets to a templates location and then > specify a template as your starting config when creating new collections via > REST API. We can have a default template that we ship with. > This will let you create collections from scratch via REST API, and then you > can use things like the schema REST API to customize the template config to > your needs. -- 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
[jira] [Commented] (SOLR-5955) Add config templates to SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559571#comment-14559571 ] Tomás Fernández Löbbe commented on SOLR-5955: - bq. Any config-set can be a template for creating another config-set. Any config-set can be marked as immutable. +1 > Add config templates to SolrCloud. > -- > > Key: SOLR-5955 > URL: https://issues.apache.org/jira/browse/SOLR-5955 > Project: Solr > Issue Type: New Feature >Reporter: Mark Miller > Attachments: SOLR-5955.patch > > > You should be able to upload config sets to a templates location and then > specify a template as your starting config when creating new collections via > REST API. We can have a default template that we ship with. > This will let you create collections from scratch via REST API, and then you > can use things like the schema REST API to customize the template config to > your needs. -- 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
[jira] [Commented] (SOLR-5955) Add config templates to SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559280#comment-14559280 ] Yonik Seeley commented on SOLR-5955: bq. we should have the concept of immutable ConfigSets, we don't need a separate concept of templates. Thoughts? Yep. Depending on how you look at it, the concepts could be rather orthogonal. Any config-set can be a template for creating another config-set. Any config-set can be marked as immutable. > Add config templates to SolrCloud. > -- > > Key: SOLR-5955 > URL: https://issues.apache.org/jira/browse/SOLR-5955 > Project: Solr > Issue Type: New Feature >Reporter: Mark Miller > Attachments: SOLR-5955.patch > > > You should be able to upload config sets to a templates location and then > specify a template as your starting config when creating new collections via > REST API. We can have a default template that we ship with. > This will let you create collections from scratch via REST API, and then you > can use things like the schema REST API to customize the template config to > your needs. -- 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
[jira] [Commented] (SOLR-5955) Add config templates to SolrCloud.
[
https://issues.apache.org/jira/browse/SOLR-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556994#comment-14556994
]
Gregory Chanan commented on SOLR-5955:
--
Some thoughts on this and SOLR-7570:
1) The motivation here is really about having some immutability around
configsets. This is important in a couple of scenarios:
a) you want built-in immutable templates that people can use to get started
quickly. This should be immutable so no one else accidently screws it up.
b) in a secure setup, you don't want end-users to write directly to zookeeper
or to disk. We've seen security complaints when we've allowed that sort of
thing in the past. Providing an immutable template that end-users can build on
and modify via Config APIs is much more sensible. Again, you want to make this
immutable so no one accidently or maliciously screws up the template.
2) A template is really just an immutable configset where instantiating creates
a mutable copy
>From a complexity POV, It seems not worth it to maintain a separate "template"
>concept if mutability is the only difference from configsets. I.e. templates
>are stored in a different location in ZK, have different zkcli commands that
>need to be maintained, would need to have separate handling from ConfigSets in
>a UI, require a different paramter in the CollectionsAPI for instantiation
>("configTemplate" above). If ConfigSets could be marked as mutable vs
>immutable, a ConfigSet API could have reasonable semantics here, like copying
>an immutable configset makes a mutable copy (since making an immutable copy
>seems pointless), or that copy is disallowed on immutable ConfigSets, instead
>you have to call a different command like "instantiate" instead. Anshum's
>idea above (/collections/collection_name/config/xxx could be implemented in
>this setup, by just creating a collection-specific mutable diff as described
>in SOLR-7570. From an engineering complexity perspective, maintaining
>mutable-vs-immutable seems a lot simpler than having templates.
That said, from the end-user-perspective referring to immutable configsets as
"templates" is great -- I think most users would immediately understand what
that means and why it is important rather than "immutable configsets." Perhaps
the correct way to go here is to allow (do we already?) configs in
subdirectories, e.g. we put all "immutable configsets" under /configs/templates
and we can refer to them as "templates" in the documentation, but they don't
need any special handling in the code compared to ConfigSets (i.e. you could
create a collection in one step via
&collection.configName=template/secureTemplate.
So, TLDR: we should have the concept of immutable ConfigSets, we don't need a
separate concept of templates. Thoughts?
> Add config templates to SolrCloud.
> --
>
> Key: SOLR-5955
> URL: https://issues.apache.org/jira/browse/SOLR-5955
> Project: Solr
> Issue Type: New Feature
>Reporter: Mark Miller
> Attachments: SOLR-5955.patch
>
>
> You should be able to upload config sets to a templates location and then
> specify a template as your starting config when creating new collections via
> REST API. We can have a default template that we ship with.
> This will let you create collections from scratch via REST API, and then you
> can use things like the schema REST API to customize the template config to
> your needs.
--
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
[jira] [Commented] (SOLR-5955) Add config templates to SolrCloud.
[
https://issues.apache.org/jira/browse/SOLR-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556395#comment-14556395
]
Anshum Gupta commented on SOLR-5955:
It sounds like what I suggested but with the ability to dynamically switch a
config-set for a collection. That might get tricky unless you're only talking
about allowing a one time move from a shared config-set to a collection
specific config-set. e.g.
# collection1 uses conf1 (shared config-set)
# you want collection1 to have it's own copy of conf1, so you make the API
call, which copies the config to another location
{{(/collections/collection1/config/... )}} ? and then links it there.
# Going forward, you could edit this config using the API without worrying
about the impact on other collections.
It would be tricky to have an API that allows collection1 to be linked to a new
config called, conf2, and then in a while switch it to say, conf3, which may or
may-not be even compatible.
> Add config templates to SolrCloud.
> --
>
> Key: SOLR-5955
> URL: https://issues.apache.org/jira/browse/SOLR-5955
> Project: Solr
> Issue Type: New Feature
>Reporter: Mark Miller
> Attachments: SOLR-5955.patch
>
>
> You should be able to upload config sets to a templates location and then
> specify a template as your starting config when creating new collections via
> REST API. We can have a default template that we ship with.
> This will let you create collections from scratch via REST API, and then you
> can use things like the schema REST API to customize the template config to
> your needs.
--
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
[jira] [Commented] (SOLR-5955) Add config templates to SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556204#comment-14556204 ] Yonik Seeley commented on SOLR-5955: Perhaps more general functionality : the ability to easily make a copy of a configset and the ability to easily switch what configset is being used for a collection. This covers a lot more usecases. Multiple collections share a configset but then you can make a new one based on the old one, switch only one collection over to it and try it out before migrating the others. The fact that something is a template vs just a normal config set could be one of convention (i.e. any configset can be a template). There could even be an implicit default template called something clever like "default_template" to cover Mark's original use case. > Add config templates to SolrCloud. > -- > > Key: SOLR-5955 > URL: https://issues.apache.org/jira/browse/SOLR-5955 > Project: Solr > Issue Type: New Feature >Reporter: Mark Miller > Attachments: SOLR-5955.patch > > > You should be able to upload config sets to a templates location and then > specify a template as your starting config when creating new collections via > REST API. We can have a default template that we ship with. > This will let you create collections from scratch via REST API, and then you > can use things like the schema REST API to customize the template config to > your needs. -- 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
[jira] [Commented] (SOLR-5955) Add config templates to SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306064#comment-14306064 ] Anshum Gupta commented on SOLR-5955: It would be good to support templates in SolrCloud but here's what I'm thinking: A user can at the time of collection creation, specify a config as a template i.e. configTemplate=xxx. This would imply 2 things: # Copy the config from /configs/xxx to /collections/config/xxx. # The copied config truly belongs to this collection and would be cleaned up when the collection gets deleted. This would work in parallel with the current concept of configSets where a config in /configs/ can be shared among multiple collections (a totally valid and practical use case). [~markrmil...@gmail.com] : Do you think I could just reuse this issue for this or should I create another issue? > Add config templates to SolrCloud. > -- > > Key: SOLR-5955 > URL: https://issues.apache.org/jira/browse/SOLR-5955 > Project: Solr > Issue Type: New Feature >Reporter: Mark Miller > Attachments: SOLR-5955.patch > > > You should be able to upload config sets to a templates location and then > specify a template as your starting config when creating new collections via > REST API. We can have a default template that we ship with. > This will let you create collections from scratch via REST API, and then you > can use things like the schema REST API to customize the template config to > your needs. -- 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
[jira] [Commented] (SOLR-5955) Add config templates to SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958896#comment-13958896 ] Mark Miller commented on SOLR-5955: --- If the default template is implicit, this also gets us to a point I've been hoping to reach: download solr start solr create mycollection -s 9 -r 3 > Add config templates to SolrCloud. > -- > > Key: SOLR-5955 > URL: https://issues.apache.org/jira/browse/SOLR-5955 > Project: Solr > Issue Type: New Feature >Reporter: Mark Miller > > You should be able to upload config sets to a templates location and then > specify a template as your starting config when creating new collections via > REST API. We can have a default template that we ship with. > This will let you create collections from scratch via REST API, and then you > can use things like the schema REST API to customize the template config to > your needs. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
