[
https://issues.apache.org/jira/browse/SOLR-11617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336864#comment-16336864
]
ASF GitHub Bot commented on SOLR-11617:
---------------------------------------
GitHub user fsparv opened a pull request:
https://github.com/apache/lucene-solr/pull/310
SOLR-11617
Changes as mentioned in Jira comment, plus rather than decide I provided an
option for the user to enable whitespace values. By default this is off and
whitespace values are treated as null, but if the user really wants to set a
value to 3 spaces they can by passing allowWhitespaceValues=true. I'm fairly
set against pure whitespace keys unless someone can supply up with a good
reason for that.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nsoft/lucene-solr SOLR-11617
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/lucene-solr/pull/310.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #310
----
commit 959401b9ac6bac5e4d696a750c3e5eb42b7da9f5
Author: gus <gus@...>
Date: 2018-01-23T19:28:11Z
SOLR 11617 - patch 2
commit 218890d7b8c01bddabd1de2a6bbe2f1735ac238c
Author: Gus Heck <gus@...>
Date: 2018-01-23T20:43:54Z
Merge branch 'master' into SOLR-11617
commit 4b4c656a107eba82ec1bfe11e8f5b14b1ea751bf
Author: Gus Heck <gus@...>
Date: 2018-01-24T03:44:46Z
adjust for package changes in master
----
> Expose Alias Metadata CRUD in REST API
> --------------------------------------
>
> Key: SOLR-11617
> URL: https://issues.apache.org/jira/browse/SOLR-11617
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: master (8.0)
> Reporter: Gus Heck
> Priority: Major
> Attachments: SOLR_11617.patch, SOLR_11617.patch
>
>
> SOLR-11487 is adding Java API for metadata on aliases, this task is to expose
> that functionality to end-users via a REST API.
> Some proposed commands, for initial discussion:
> - *SETALIASMETA* - upsert, or delete if blank/null/white-space provided.
> - *GETALIASMETA* - read existing alias metadata
> Given that the parent ticket to this task is going to rely on the alias
> metadata, and I suspect a user would potentially completely break their time
> partitioned data configuration by editing system metadata directly, we should
> either document these commands as "use at your own risk, great
> power/responsibility etc" or consider protecting some subset of metadata.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
