[jira] [Commented] (SOLR-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101733#comment-15101733 ] Mark Miller commented on SOLR-8131: --- What part was broken? Now you can't create a core because it makes you specify a schema.xml, which will fail. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar >Assignee: Varun Thacker > Labels: difficulty-easy, impact-high > Fix For: 5.5, Trunk > > Attachments: SOLR-8131-schemaless-fix.patch, > SOLR-8131-schemaless-fix.patch, SOLR-8131.patch, SOLR-8131.patch, > SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch, SOLR-8131_5x.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101033#comment-15101033 ] Mark Miller commented on SOLR-8131: --- I think this made it so that you cannot use the Admin UI to add a SolrCore out of the box? I think that's a tough user experience. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar >Assignee: Varun Thacker > Labels: difficulty-easy, impact-high > Fix For: 5.5, Trunk > > Attachments: SOLR-8131-schemaless-fix.patch, > SOLR-8131-schemaless-fix.patch, SOLR-8131.patch, SOLR-8131.patch, > SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch, SOLR-8131_5x.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101380#comment-15101380 ] Varun Thacker commented on SOLR-8131: - Hi Mark, Sorry I didn't quite follow your comment. Are you saying that the Admin UI to add a core is broken? I think that didn't work out of the box in earlier versions as well. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar >Assignee: Varun Thacker > Labels: difficulty-easy, impact-high > Fix For: 5.5, Trunk > > Attachments: SOLR-8131-schemaless-fix.patch, > SOLR-8131-schemaless-fix.patch, SOLR-8131.patch, SOLR-8131.patch, > SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch, SOLR-8131_5x.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15057547#comment-15057547 ] ASF subversion and git services commented on SOLR-8131: --- Commit 1720083 from sha...@apache.org in branch 'dev/trunk' [ https://svn.apache.org/r1720083 ] SOLR-8131: Use SolrResourceLoader to instantiate ManagedIndexSchemaFactory when no schema factory is specified in solrconfig.xml > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar >Assignee: Varun Thacker > Labels: difficulty-easy, impact-high > Fix For: 5.5, Trunk > > Attachments: SOLR-8131-schemaless-fix.patch, > SOLR-8131-schemaless-fix.patch, SOLR-8131.patch, SOLR-8131.patch, > SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch, SOLR-8131_5x.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15057539#comment-15057539 ] Shalin Shekhar Mangar commented on SOLR-8131: - Cool, I'll commit this then. All tests pass. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar >Assignee: Varun Thacker > Labels: difficulty-easy, impact-high > Fix For: 5.5, Trunk > > Attachments: SOLR-8131-schemaless-fix.patch, > SOLR-8131-schemaless-fix.patch, SOLR-8131.patch, SOLR-8131.patch, > SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch, SOLR-8131_5x.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[
https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15057530#comment-15057530
]
Varun Thacker commented on SOLR-8131:
-
Yes we have a test for that - {{TestManagedSchema#testDefaultSchemaFactory}} .
Okay so then we don't need to randomize here..
> Make ManagedIndexSchemaFactory as the default in Solr
> -
>
> Key: SOLR-8131
> URL: https://issues.apache.org/jira/browse/SOLR-8131
> Project: Solr
> Issue Type: Wish
> Components: Data-driven Schema, Schema and Analysis
>Reporter: Shalin Shekhar Mangar
>Assignee: Varun Thacker
> Labels: difficulty-easy, impact-high
> Fix For: 5.5, Trunk
>
> Attachments: SOLR-8131-schemaless-fix.patch,
> SOLR-8131-schemaless-fix.patch, SOLR-8131.patch, SOLR-8131.patch,
> SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch, SOLR-8131_5x.patch
>
>
> The techproducts and other examples shipped with Solr all use the
> ClassicIndexSchemaFactory which disables all Schema APIs which need to modify
> schema. It'd be nice to be able to support both read/write schema APIs
> without needing to enable data-driven or schema-less mode.
> I propose to change all 5.x examples to explicitly use
> ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default
> in trunk (6.x).
--
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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15057498#comment-15057498 ] Varun Thacker commented on SOLR-8131: - Hi Shalin, Does it make sent to have TestCloudSchemaless randomize between two solrconfig.xml's instead? One which explicitly specifies managed-schema and one which doesn't? > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar >Assignee: Varun Thacker > Labels: difficulty-easy, impact-high > Fix For: 5.5, Trunk > > Attachments: SOLR-8131-schemaless-fix.patch, > SOLR-8131-schemaless-fix.patch, SOLR-8131.patch, SOLR-8131.patch, > SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch, SOLR-8131_5x.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15057514#comment-15057514 ] Shalin Shekhar Mangar commented on SOLR-8131: - I was assuming that we have a test which will fail if no index schema factory definition defaults to ClassicIndexSchemaFactory accidentally? > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar >Assignee: Varun Thacker > Labels: difficulty-easy, impact-high > Fix For: 5.5, Trunk > > Attachments: SOLR-8131-schemaless-fix.patch, > SOLR-8131-schemaless-fix.patch, SOLR-8131.patch, SOLR-8131.patch, > SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch, SOLR-8131_5x.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15048196#comment-15048196 ] ASF subversion and git services commented on SOLR-8131: --- Commit 1718768 from [~varunthacker] in branch 'dev/trunk' [ https://svn.apache.org/r1718768 ] SOLR-8131: example/files config doesn't explicitly mention a schema factory + imporove upgrading instructions > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar >Assignee: Varun Thacker > Labels: difficulty-easy, impact-high > Fix For: Trunk, 5.5 > > Attachments: SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch, > SOLR-8131.patch, SOLR-8131.patch, SOLR-8131_5x.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044580#comment-15044580 ] ASF subversion and git services commented on SOLR-8131: --- Commit 1718264 from [~varunthacker] in branch 'dev/trunk' [ https://svn.apache.org/r1718264 ] SOLR-8131: Add CHANGES entry under solr 5.4 as well mentioning change to ManagedIndexSchemaFactory in all example config files > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > Attachments: SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch, > SOLR-8131.patch, SOLR-8131.patch, SOLR-8131_5x.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044612#comment-15044612 ] ASF subversion and git services commented on SOLR-8131: --- Commit 1718265 from [~varunthacker] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1718265 ] SOLR-8131: Make ManagedIndexSchemaFactory the default schemaFactory in all example config files > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > Attachments: SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch, > SOLR-8131.patch, SOLR-8131.patch, SOLR-8131_5x.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044780#comment-15044780 ] ASF subversion and git services commented on SOLR-8131: --- Commit 1718307 from [~varunthacker] in branch 'dev/trunk' [ https://svn.apache.org/r1718307 ] SOLR-8131: fix test solrconfig.xml files for the contrib modules > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar >Assignee: Varun Thacker > Labels: difficulty-easy, impact-high > Fix For: Trunk, 5.5 > > Attachments: SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch, > SOLR-8131.patch, SOLR-8131.patch, SOLR-8131_5x.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044507#comment-15044507 ] ASF subversion and git services commented on SOLR-8131: --- Commit 1718258 from [~varunthacker] in branch 'dev/trunk' [ https://svn.apache.org/r1718258 ] SOLR-8131: Make ManagedIndexSchemaFactory the default schemaFactory when luceneMatchVersion >= 6 > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > Attachments: SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch, > SOLR-8131.patch, SOLR-8131.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[
https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037493#comment-15037493
]
Shalin Shekhar Mangar commented on SOLR-8131:
-
Thanks Varun, there's one reproducible test failure with your patch applied:
{code}
[junit4] 2> NOTE: reproduce with: ant test
-Dtestcase=TestSolrCLIRunExample -Dtests.method=testInteractiveSolrCloudExample
-Dtests.seed=B06DF3AE906F4D27 -Dtests.slow=true -Dtests.locale=es_PY
-Dtests.timezone=Pacific/Easter -Dtests.asserts=true -Dtests.file.encoding=UTF-8
[junit4] ERROR 5.32s J1 |
TestSolrCLIRunExample.testInteractiveSolrCloudExample <<<
[junit4]> Throwable #1:
org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException: Error from
server at http://localhost:54786/solr/testCloudExamplePrompt_shard1_replica2:
This IndexSchema is not mutable.
[junit4]>at
__randomizedtesting.SeedInfo.seed([B06DF3AE906F4D27:6B1C1364A71A8841]:0)
[junit4]>at
org.apache.solr.client.solrj.impl.CloudSolrClient.directUpdate(CloudSolrClient.java:633)
[junit4]>at
org.apache.solr.client.solrj.impl.CloudSolrClient.sendRequest(CloudSolrClient.java:982)
[junit4]>at
org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:871)
[junit4]>at
org.apache.solr.client.solrj.impl.CloudSolrClient.request(CloudSolrClient.java:807)
[junit4]>at
org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:150)
[junit4]>at
org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:174)
[junit4]>at
org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:139)
[junit4]>at
org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:153)
[junit4]>at
org.apache.solr.util.TestSolrCLIRunExample.testInteractiveSolrCloudExample(TestSolrCLIRunExample.java:445)
[junit4]>at java.lang.Thread.run(Thread.java:745)
[junit4]> Caused by:
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error
from server at
http://localhost:54786/solr/testCloudExamplePrompt_shard1_replica2: This
IndexSchema is not mutable.
[junit4]>at
org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:575)
[junit4]>at
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:241)
[junit4]>at
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:230)
[junit4]>at
org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:372)
[junit4]>at
org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:325)
[junit4]>at
org.apache.solr.client.solrj.impl.CloudSolrClient$2.call(CloudSolrClient.java:608)
[junit4]>at
org.apache.solr.client.solrj.impl.CloudSolrClient$2.call(CloudSolrClient.java:605)
[junit4]>at
java.util.concurrent.FutureTask.run(FutureTask.java:266)
[junit4]>at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor$1.run(ExecutorUtil.java:232)
[junit4]>at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[junit4]>at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[junit4]>... 1 more
{code}
> Make ManagedIndexSchemaFactory as the default in Solr
> -
>
> Key: SOLR-8131
> URL: https://issues.apache.org/jira/browse/SOLR-8131
> Project: Solr
> Issue Type: Wish
> Components: Data-driven Schema, Schema and Analysis
>Reporter: Shalin Shekhar Mangar
> Labels: difficulty-easy, impact-high
> Fix For: 5.4, Trunk
>
> Attachments: SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch
>
>
> The techproducts and other examples shipped with Solr all use the
> ClassicIndexSchemaFactory which disables all Schema APIs which need to modify
> schema. It'd be nice to be able to support both read/write schema APIs
> without needing to enable data-driven or schema-less mode.
> I propose to change all 5.x examples to explicitly use
> ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default
> in trunk (6.x).
--
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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[
https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037788#comment-15037788
]
Shalin Shekhar Mangar commented on SOLR-8131:
-
There are still some test failures, Varun
{code}
[junit4] Tests with failures [seed: EF2ABB6034EFC3BC]:
[junit4] - org.apache.solr.analytics.facet.FieldFacetTest (suite)
[junit4] - org.apache.solr.analytics.expression.ExpressionTest (suite)
[junit4] - org.apache.solr.analytics.NoFacetTest (suite)
[junit4] - org.apache.solr.analytics.util.valuesource.FunctionTest (suite)
[junit4] - org.apache.solr.analytics.facet.RangeFacetTest (suite)
[junit4] - org.apache.solr.analytics.facet.FieldFacetExtrasTest (suite)
[junit4] - org.apache.solr.analytics.facet.QueryFacetTest (suite)
{code}
Most are of the form:
{code}
[junit4] ERROR 0.00s J1 | QueryFacetTest (suite) <<<
[junit4]> Throwable #1: java.security.AccessControlException: access
denied ("java.io.FilePermission"
"/home/shalin/work/oss/trunk/solr/contrib/analytics/src/test-files/solr/collection1/conf/managed-schema"
"write")
[junit4]>at
__randomizedtesting.SeedInfo.seed([EF2ABB6034EFC3BC]:0)
[junit4]>at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
[junit4]>at
java.security.AccessController.checkPermission(AccessController.java:884)
[junit4]>at
java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
[junit4]>at
java.lang.SecurityManager.checkWrite(SecurityManager.java:979)
[junit4]>at
java.io.FileOutputStream.(FileOutputStream.java:200)
[junit4]>at
java.io.FileOutputStream.(FileOutputStream.java:162)
[junit4]>at
org.apache.solr.schema.ManagedIndexSchema.persistManagedSchema(ManagedIndexSchema.java:130)
[junit4]>at
org.apache.solr.schema.ManagedIndexSchemaFactory.upgradeToManagedSchema(ManagedIndexSchemaFactory.java:271)
[junit4]>at
org.apache.solr.schema.ManagedIndexSchemaFactory.create(ManagedIndexSchemaFactory.java:186)
[junit4]>at
org.apache.solr.schema.ManagedIndexSchemaFactory.create(ManagedIndexSchemaFactory.java:46)
[junit4]>at
org.apache.solr.schema.IndexSchemaFactory.buildIndexSchema(IndexSchemaFactory.java:75)
[junit4]>at
org.apache.solr.util.TestHarness.(TestHarness.java:97)
[junit4]>at
org.apache.solr.SolrTestCaseJ4.createCore(SolrTestCaseJ4.java:572)
[junit4]>at
org.apache.solr.SolrTestCaseJ4.initCore(SolrTestCaseJ4.java:562)
[junit4]>at
org.apache.solr.SolrTestCaseJ4.initCore(SolrTestCaseJ4.java:404)
[junit4]>at
org.apache.solr.SolrTestCaseJ4.initCore(SolrTestCaseJ4.java:393)
[junit4]>at
org.apache.solr.analytics.facet.QueryFacetTest.beforeClass(QueryFacetTest.java:39)
[junit4]>at java.lang.Thread.run(Thread.java:745)
{code}
> Make ManagedIndexSchemaFactory as the default in Solr
> -
>
> Key: SOLR-8131
> URL: https://issues.apache.org/jira/browse/SOLR-8131
> Project: Solr
> Issue Type: Wish
> Components: Data-driven Schema, Schema and Analysis
>Reporter: Shalin Shekhar Mangar
> Labels: difficulty-easy, impact-high
> Fix For: 5.4, Trunk
>
> Attachments: SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch,
> SOLR-8131.patch
>
>
> The techproducts and other examples shipped with Solr all use the
> ClassicIndexSchemaFactory which disables all Schema APIs which need to modify
> schema. It'd be nice to be able to support both read/write schema APIs
> without needing to enable data-driven or schema-less mode.
> I propose to change all 5.x examples to explicitly use
> ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default
> in trunk (6.x).
--
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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[
https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037376#comment-15037376
]
Varun Thacker commented on SOLR-8131:
-
Hi Erik,
bq. ShowFileRequestHandlerTest.java: maybe use the
DEFAULT_MANAGED_SCHEMA_RESOURCE_NAME constant instead on "QueryRequest request
= new QueryRequest(params("file","managed-schema"));"
I didn't make this change. The argument being we should leave hardcoded
constants in our tests. That way is someone in the future accidentally changed
DEFAULT_MANAGED_SCHEMA_RESOURCE_NAME the tests would atleast catch it as a
break.
bq. explicitly in all the shipped configs and just leave it out entirely. (for
one, no one really needs to change the resource name)
Incorporated in the patch
> Make ManagedIndexSchemaFactory as the default in Solr
> -
>
> Key: SOLR-8131
> URL: https://issues.apache.org/jira/browse/SOLR-8131
> Project: Solr
> Issue Type: Wish
> Components: Data-driven Schema, Schema and Analysis
>Reporter: Shalin Shekhar Mangar
> Labels: difficulty-easy, impact-high
> Fix For: 5.4, Trunk
>
> Attachments: SOLR-8131.patch, SOLR-8131.patch, SOLR-8131.patch
>
>
> The techproducts and other examples shipped with Solr all use the
> ClassicIndexSchemaFactory which disables all Schema APIs which need to modify
> schema. It'd be nice to be able to support both read/write schema APIs
> without needing to enable data-driven or schema-less mode.
> I propose to change all 5.x examples to explicitly use
> ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default
> in trunk (6.x).
--
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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[
https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035820#comment-15035820
]
Erik Hatcher commented on SOLR-8131:
[~varunthacker] - here's some feedback on that patch:
* ShowFileRequestHandlerTest.java: maybe use the
DEFAULT_MANAGED_SCHEMA_RESOURCE_NAME constant instead on "QueryRequest request
= new QueryRequest(params("file","managed-schema"));"
* In the spirit of less (explicit) config, we could maybe get away from
specifying this incantation
{code}
+
+true
+managed-schema
+
{code}
explicitly in all the shipped configs and just leave it out entirely. (for
one, no one really needs to change the resource name)
* I like the test of managed schema being set in the shipped configs!
> Make ManagedIndexSchemaFactory as the default in Solr
> -
>
> Key: SOLR-8131
> URL: https://issues.apache.org/jira/browse/SOLR-8131
> Project: Solr
> Issue Type: Wish
> Components: Data-driven Schema, Schema and Analysis
>Reporter: Shalin Shekhar Mangar
> Labels: difficulty-easy, impact-high
> Fix For: 5.4, Trunk
>
> Attachments: SOLR-8131.patch, SOLR-8131.patch
>
>
> The techproducts and other examples shipped with Solr all use the
> ClassicIndexSchemaFactory which disables all Schema APIs which need to modify
> schema. It'd be nice to be able to support both read/write schema APIs
> without needing to enable data-driven or schema-less mode.
> I propose to change all 5.x examples to explicitly use
> ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default
> in trunk (6.x).
--
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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15021617#comment-15021617 ] Varun Thacker commented on SOLR-8131: - bq. Those with static schemas never changed should (In my opinion) still use the classic schema factory. Makes sense. I'll work on a new patch where these static schemas use the classic schema factory. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > Attachments: SOLR-8131.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15020927#comment-15020927 ] Uwe Schindler commented on SOLR-8131: - OK. So why do you want to change those configs to use managed schema at all? Those are static test only schema, never changed. The classic schema factory is not deprecated and should never be. So why not leave the "test schemas" as they are. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > Attachments: SOLR-8131.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[
https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15020943#comment-15020943
]
Ishan Chattopadhyaya commented on SOLR-8131:
bq. All tests that use the manages schema factory have to be rewritten to use
SolrTestcaseJ4's copy functionality to create a writeable clone.
Not sure if this helps here, but I once wrote a test based on managed schema,
{{SpatialRPTFieldTypeTest}} (extends AbstractBadConfigTestBase, which extends
SolrTestcaseJ4).
AFAICT, that test copied all configs and schemas specified into temp directory.
Then, it tried to find "managed-schema", couldn't find it and loaded
schema-minimal.xml after copying it over to "managed-schema".
{noformat}
o.a.s.s.ManagedIndexSchemaFactory The schema is configured as managed, but
managed schema resource managed-schema not found - loading non-managed schema
schema-minimal.xml instead
{noformat}
Do you think the needed schema file for each test can be copied over to the
temp directory as "schema-minimal.xml", from where it gets loaded up as
"managed-schema"?
> Make ManagedIndexSchemaFactory as the default in Solr
> -
>
> Key: SOLR-8131
> URL: https://issues.apache.org/jira/browse/SOLR-8131
> Project: Solr
> Issue Type: Wish
> Components: Data-driven Schema, Schema and Analysis
>Reporter: Shalin Shekhar Mangar
> Labels: difficulty-easy, impact-high
> Fix For: 5.4, Trunk
>
> Attachments: SOLR-8131.patch
>
>
> The techproducts and other examples shipped with Solr all use the
> ClassicIndexSchemaFactory which disables all Schema APIs which need to modify
> schema. It'd be nice to be able to support both read/write schema APIs
> without needing to enable data-driven or schema-less mode.
> I propose to change all 5.x examples to explicitly use
> ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default
> in trunk (6.x).
--
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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[
https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15020913#comment-15020913
]
Uwe Schindler commented on SOLR-8131:
-
I still don't understand why you cannot use the follwoing approach as described
before! Run all tests *one time* with {{-Dtests.useSecurityManager=false}}.
After this test run, all schema files should be renamed accordingly. All later
runs then would not need write access anymore, so security manager can be
enabled again. To persist the modified/renamed schemas just commit the changes
after the run without security manager.
> Make ManagedIndexSchemaFactory as the default in Solr
> -
>
> Key: SOLR-8131
> URL: https://issues.apache.org/jira/browse/SOLR-8131
> Project: Solr
> Issue Type: Wish
> Components: Data-driven Schema, Schema and Analysis
>Reporter: Shalin Shekhar Mangar
> Labels: difficulty-easy, impact-high
> Fix For: 5.4, Trunk
>
> Attachments: SOLR-8131.patch
>
>
> The techproducts and other examples shipped with Solr all use the
> ClassicIndexSchemaFactory which disables all Schema APIs which need to modify
> schema. It'd be nice to be able to support both read/write schema APIs
> without needing to enable data-driven or schema-less mode.
> I propose to change all 5.x examples to explicitly use
> ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default
> in trunk (6.x).
--
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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15020911#comment-15020911 ] Uwe Schindler commented on SOLR-8131: - bq. renames it to a file called managed-schema or to a name explicitly mentioned. Why not specify "schema.xml" as the specified schema name? I have no idea why we need a different name here? In any case, we cannot allow write access to src/test-files! So 2 possibilities: - Fix all schema/configs throughout solr - tests that directly access the test-files folder have to copy to a temporary dir (like most tests already do). There is some utility method in SolrTestcaseJ4 / TestHarness to do this (I think). > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > Attachments: SOLR-8131.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15020915#comment-15020915 ] Varun Thacker commented on SOLR-8131: - Hi Uwe, The problem is , we have lots of schema-*.xml / solrconfig-*.xmlfiles under test-files/solr/collection1/conf . ManagedSchemaIndexFactory will rename a schema file to "managed-schema" . So the test runs will overwrite the same file when run without the security manager. We cannot even specify a specific name instead of "managed-schema" in the solrconfig.xml files since a test can use any combination of solrconfig/schema files.. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > Attachments: SOLR-8131.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15020946#comment-15020946 ] Uwe Schindler commented on SOLR-8131: - bq. I'm assuming that all tests would have a different temp directory, so there won't be a conflict there. Exactly. This is why I said, that all tests that actually modify the schmea, have to be copied over. Those with static schemas never changed should (In my opinion) still use the classic schema factory. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > Attachments: SOLR-8131.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15020835#comment-15020835 ] Varun Thacker commented on SOLR-8131: - The way ManagedSchemaFactory initializes itself is that it looks for the default schema file ( "managed-schema" ) . If it's not present then it takes the specified schema-name.xml ( default is schema.xml ) and renames it to a file called managed-schema or to a name explicitly mentioned. We have lots of solrconfigs and schema files in a common directory and each test can use any combination of that. Since we need to specify the new managed-schema file name in the solrconfig file and that a test can use any combination we can't manually change anything either. I don't see a way where we can have multiple schema/solrconfig files in the same directory and support any renaming logic from ManagedSchemaFactory > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > Attachments: SOLR-8131.patch > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[
https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15020393#comment-15020393
]
Uwe Schindler commented on SOLR-8131:
-
bq. I have no idea how to make the tests pass with this change. We rewrite all
the schema files to managed-schema . Firstly we need to give the tests write
permissions to managed-schema ( solr-tests.policy ) . More importantly tests
which don't run in their own VM will overwrite the files under
test-files/solr/collection1/solr ?
Please don't do this permanently! Maybe only rewrite the old schemas once
(automatically), disabling the security manager (e.g. run tests with
{{-Dtests.useSecurityManager=false}}). After that all schemas should be
converted. Then just cleanup the directory and remove the old files and commit
the changes. After that nothing should change the schemas anymore?
The general rule is to make a clone of the core directory for tests that
actually modify the core directory, e.g. update the schema. Most tests already
do this.
> Make ManagedIndexSchemaFactory as the default in Solr
> -
>
> Key: SOLR-8131
> URL: https://issues.apache.org/jira/browse/SOLR-8131
> Project: Solr
> Issue Type: Wish
> Components: Data-driven Schema, Schema and Analysis
>Reporter: Shalin Shekhar Mangar
> Labels: difficulty-easy, impact-high
> Fix For: 5.4, Trunk
>
> Attachments: SOLR-8131.patch
>
>
> The techproducts and other examples shipped with Solr all use the
> ClassicIndexSchemaFactory which disables all Schema APIs which need to modify
> schema. It'd be nice to be able to support both read/write schema APIs
> without needing to enable data-driven or schema-less mode.
> I propose to change all 5.x examples to explicitly use
> ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default
> in trunk (6.x).
--
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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948377#comment-14948377 ] Varun Thacker commented on SOLR-8131: - bq. What I'd like to see is the techproducts sample stay the same (it has always been a static schema, let it stay that way), but update the bin/solr script (or such) to upload a standard managed schema config on first start up I don't think thats a good idea. We might end up having the same issue we had with collection1 . If ManagedIndexSchemaFactory is by default we can have the schema editor thats in your plan without any problems? > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[
https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948364#comment-14948364
]
Noble Paul commented on SOLR-8131:
--
[~upayavira] why do you think the people will resist moving to the new admin
UI. I don't remember seeing any discussion where people are opposed to it.
bq. I'm NOT knocking it as an API call, it's a perfectly fine API, but I'm sure
not going to be happy typing it out 100 times for adding 100 fields to my
schema. Or writing a script.
I see the pain [~erickerickson] .
Apart from what is proposed in SOLR-8139 , we should add a {{modify-field}}
command where you can just update one value of the field
e.g
{code}
curl -X POST -H 'Content-type:application/json' --data-binary '{
"add-field":
{ "name":"sell-by", "stored":true }
}' http://localhost:8983/solr/gettingstarted/schema
{code}
We should provide a simple admin page where I can type arbitrary commands to an
endpoint . So all I need to do is type
{code}
{
"modify-field":
{ "name":"sell-by", "stored":true }
}
{code}
We plan to support hocon as well. so all you need to type would be
{code}
modify-field {name:sell-by, stored:true}
{code}
> Make ManagedIndexSchemaFactory as the default in Solr
> -
>
> Key: SOLR-8131
> URL: https://issues.apache.org/jira/browse/SOLR-8131
> Project: Solr
> Issue Type: Wish
> Components: Data-driven Schema, Schema and Analysis
>Reporter: Shalin Shekhar Mangar
> Labels: difficulty-easy, impact-high
> Fix For: 5.4, Trunk
>
>
> The techproducts and other examples shipped with Solr all use the
> ClassicIndexSchemaFactory which disables all Schema APIs which need to modify
> schema. It'd be nice to be able to support both read/write schema APIs
> without needing to enable data-driven or schema-less mode.
> I propose to change all 5.x examples to explicitly use
> ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default
> in trunk (6.x).
--
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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948410#comment-14948410 ] Upayavira commented on SOLR-8131: - What I want is a way to say "when you start, start with some configs". Equally there can be a "start without configs" option. Or, an API that says "load a sample config set from disk (i.e from server/solr/configsets) so the user can bootstrap via the UI from one of the known provided configsets. Is the intention that a non-managed schema be deprecated? If not, I'd like there to be an example that works that way, and techproducts seems like a reasonable candidate. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948414#comment-14948414 ] Upayavira commented on SOLR-8131: - bq: Upayavira why do you think the people will resist moving to the new admin UI. I don't remember seeing any discussion where people are opposed to it. Because people don't like change. Because once people start using the new UI, I put money on the fact that they will start finding all sorts of details that I haven't considered. Giving some new features at least counterbalances that risk somewhat. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14947514#comment-14947514 ] Upayavira commented on SOLR-8131: - No, I don't want to create a collection. I want an empty managed-schema config set to be uploaded to a SolrCloud setup, either by default, or with a single switch on the bin/solr start command. Or... an extension to the configset API that says "load one of these standard configsets from disk", e.g: /admin/configs?action=LOAD=managed_schema There's no real security risks here, as the files are coming off disk. It allows the UI to pull in one of a set of sample configsets from the server/solr/configsets directory. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14947500#comment-14947500 ] Alexandre Rafalovitch commented on SOLR-8131: - You mean "bin/solr create_core -d", right? As a standard configset! Stored in the same place as the others, etc. Just checking? Otherwise, yet another way to create the collection would cause confusion. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14947525#comment-14947525 ] Upayavira commented on SOLR-8131: - bq. I'm sure 8139 will drive people toward the new admin UI as well... That's my idea. Make the new UI visible via the "new UI" link, then start jamming it so full of new features that people will *demand* that it be made the default! > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14947263#comment-14947263 ] Upayavira commented on SOLR-8131: - What I'd like to see is the techproducts sample stay the same (it has always been a static schema, let it stay that way), but update the bin/solr script (or such) to upload a standard managed schema config on first start up - or allow it via an argument: bin/solr -conf managed start That way, once the server is started, everything needed can be done via the UI. I'd love to see this soon, as I want to use it in my talk at LuceneRevolution next week!! I'll also add basic "add field", "add dynamic field" and "copy field" support to the schema browser in time for that talk also :-) What I'm saying is - there's no such thing as default configset anymore. What I'd suggest is that Solr starts with a single configset uploaded, which is in managed schema mode, or there is a very easy way to do it, on startup. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14947366#comment-14947366 ] Erick Erickson commented on SOLR-8131: -- Guess this kind of makes the discussion about whether 8139 should block this irrelevant doesn't it ;) I'm sure 8139 will drive people toward the new admin UI as well... > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: 5.4, Trunk > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[
https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14947230#comment-14947230
]
Erick Erickson commented on SOLR-8131:
--
Apologies in advance if I'm missing something here and don't get me wrong, I
love where this could go; "use solr/bin to set up your test cluster then go to
the admin UI to modify your configs" would simplify _greatly_ the new user
experience.
The current "use zkcli to update your config set after you make changes" is
_really_ clumsy and I've seen countless users confused by this, especially
misunderstanding of the bootstrapping options. Not to mention all the confusion
when a manual edit introduces a syntax error and we get "help me, all of the
sudden Solr doesn't start"
However (you knew this was coming):
If this is the default, then the only way to modify the schema will be with the
Schema API, right? So rather than allow someone to get into the schema file and
do a bunch of manual edits we'll force them to issue some long command like
below. I'm _NOT_ knocking it as an API call, it's a perfectly fine API, but I'm
sure not going to be happy typing it out 100 times for adding 100 fields to my
schema. Or writing a script.
curl -X POST -H 'Content-type:application/json' --data-binary '{
"add-field":{
"name":"sell-by",
"type":"tdate",
"stored":true }
}' http://localhost:8983/solr/gettingstarted/schema
Sure, I can do all the mods to schema.xml first then switch to managed, but
that's obscure and certainly not something that someone would even think about
when just starting out. Or we can tell a novice to ignore the message about
"generated by... do not modify".
So my proposal would be do one of two things:
1> provide a "schema builder" as part of the new Angular Admin. Wouldn't have
to be anything all that complex to start and could grow over time. I can
imagine several approaches that would be more or less work, discuss this in any
tickets that come up I suppose.
or
2> enhance the bin/solr script to add/delete/replace schema elements. I'd
really like this option to allow changing one and only one parameter as an
option (syntax TBD) to make it simple to, say, just change stored from "true"
to "false" for some field/fieldType.
3> ???
I prefer <1> by _far_, but "progress not perfection" is the goal here. And this
could be quite a simple UI, we'd of course have to be careful that it didn't
upload arbitrary XML, but that should be relatively simple.
I'd go so far as advocate that whatever we decide about <1> or <2> be put in a
JIRA that _blocks_ this one. I can be talked out of that, especially if making
a UI that used the managed schema stuff under the covers would take a long time.
> Make ManagedIndexSchemaFactory as the default in Solr
> -
>
> Key: SOLR-8131
> URL: https://issues.apache.org/jira/browse/SOLR-8131
> Project: Solr
> Issue Type: Wish
> Components: Data-driven Schema, Schema and Analysis
>Reporter: Shalin Shekhar Mangar
> Labels: difficulty-easy, impact-high
> Fix For: 5.4, Trunk
>
>
> The techproducts and other examples shipped with Solr all use the
> ClassicIndexSchemaFactory which disables all Schema APIs which need to modify
> schema. It'd be nice to be able to support both read/write schema APIs
> without needing to enable data-driven or schema-less mode.
> I propose to change all 5.x examples to explicitly use
> ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default
> in trunk (6.x).
--
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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14945039#comment-14945039 ] Alexandre Rafalovitch commented on SOLR-8131: - What about all the embedded documentation in the examples that disappears on the first run with managed schema? Including all the commented-out sections and "this is default" sections. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: Trunk, 5.4 > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14945013#comment-14945013 ] Shalin Shekhar Mangar commented on SOLR-8131: - bq. Just to clarify what we'll have is a `managed-schema` file and no `schema.xml` file in the default configs right? Yeah, I think the default is to rename any existing schema.xml file to schema.xml.bak and afterwards use 'managed-schema' as the generated schema file name. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: Trunk, 5.4 > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14945064#comment-14945064 ] Alexandre Rafalovitch commented on SOLR-8131: - I would be all over anything that's self-documenting. API endpoints, analyzers, etc. For API, something like http://swagger.io/ could help. That would enable other newbie-oriented use cases too. E.g. auto-generated UI for https://www.getpostman.com/ . This deserves its own discussion, really. A page in ref-guide could be a - simpler - option too, especially if the comments are hyperlinked into the specific guide sections. That would give people jump off points from the context of the config file into more detailed descriptions. > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: Trunk, 5.4 > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14945010#comment-14945010 ] Varun Thacker commented on SOLR-8131: - +1 Just to clarify what we'll have is a `managed-schema` file and no `schema.xml` file in the default configs right? > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: Trunk, 5.4 > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14945019#comment-14945019 ] Varun Thacker commented on SOLR-8131: - bq. Yeah, I think the default is to rename any existing schema.xml file to schema.xml.bak and afterwards use 'managed-schema' as the generated schema file name. The current data_driven config doesn't have a schema.bak file . Also if we enable it by default in 6.0 is the "mutable" flag useful then? > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: Trunk, 5.4 > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14945050#comment-14945050 ] Shalin Shekhar Mangar commented on SOLR-8131: - bq. The current data_driven config doesn't have a schema.bak file That's because the data driven config does not have a schema.xml and starts off directly with a managed-schema file. The techproducts and basic configs example do have a schema.xml (which I wasn't planning on removing) which will be renamed to schema.xml.bak bq. What about all the embedded documentation in the examples that disappears on the first run with managed schema? Including all the commented-out sections and "this is default" sections. Good point, Alexandre. What do you think we should do? Maybe we can create a page in the ref guide which has all that information instead? Another option (don't know how feasible it'd be) is to have a describe mode in the /schema API which prints helpful documentation about every enabled option/plugin in the schema? > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: Trunk, 5.4 > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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-8131) Make ManagedIndexSchemaFactory as the default in Solr
[ https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14945005#comment-14945005 ] Noble Paul commented on SOLR-8131: -- > Make ManagedIndexSchemaFactory as the default in Solr > - > > Key: SOLR-8131 > URL: https://issues.apache.org/jira/browse/SOLR-8131 > Project: Solr > Issue Type: Wish > Components: Data-driven Schema, Schema and Analysis >Reporter: Shalin Shekhar Mangar > Labels: difficulty-easy, impact-high > Fix For: Trunk, 5.4 > > > The techproducts and other examples shipped with Solr all use the > ClassicIndexSchemaFactory which disables all Schema APIs which need to modify > schema. It'd be nice to be able to support both read/write schema APIs > without needing to enable data-driven or schema-less mode. > I propose to change all 5.x examples to explicitly use > ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default > in trunk (6.x). -- 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
