[
https://issues.apache.org/jira/browse/SOLR-6476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151128#comment-14151128
]
Noble Paul commented on SOLR-6476:
----------------------------------
bq.A while ago, Stefan and I tried to allow schema.xml to be edited from the
admin UI.
I want to move to a system where the users are not aware of schema.xml . It
should be an internal detail. Exactly the same way I deal with my
RDBMS/Cassandra (or whatever) . The way a user thinks of my RDBMS is as follows
* Startup the server first
* use A DDL to create a schema
* During the lifecycle of the system I use more DDL to add/remove fields
* I use a command like "describe table' to know the current schema. (We have a
REST API )
* I don't really care about how the server stores the schema/config or whatever
To achieve tis goal , we must stop thinking about the system in terms of xmls
and we should start thinking about the APIs as the DDL for Solr.
The term 'managed schema' will have no relevance. schema will always be
'managed' and the the adjective 'managed' must go away
> Create a bulk mode for schema API
> ---------------------------------
>
> Key: SOLR-6476
> URL: https://issues.apache.org/jira/browse/SOLR-6476
> Project: Solr
> Issue Type: Bug
> Components: Schema and Analysis
> Reporter: Noble Paul
> Assignee: Noble Paul
> Labels: managedResource
> Attachments: SOLR-6476.patch, SOLR-6476.patch, SOLR-6476.patch,
> SOLR-6476.patch, SOLR-6476.patch, SOLR-6476.patch, SOLR-6476.patch
>
>
> The current schema API does one operation at a time and the normal usecase is
> that users add multiple fields/fieldtypes/copyFields etc in one shot.
> example
> {code:javascript}
> curl http://localhost:8983/solr/collection1/schema -H
> 'Content-type:application/json' -d '{
> "add-field": {
> "name":"sell-by",
> "type":"tdate",
> "stored":true
> },
> "add-field":{
> "name":"catchall",
> "type":"text_general",
> "stored":false
> }
> }
> {code}
--
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
