[
https://issues.apache.org/jira/browse/SOLR-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046634#comment-15046634
]
Upayavira commented on SOLR-8386:
---------------------------------
This is what does it:
{code}
Config.get({core: $routeParams.core}, function(data) {
$scope.isSchemaUpdatable = data.config.schemaFactory.class ==
"ManagedIndexSchemaFactory";
});
{code}
i.e. it calls the config API, and looks to see what schema factory is
configured. If it is the Managed one, then it switches on those buttons.
Config.get() calls /solr/<collection>/config - what do you get from calling
that URL, especially inside config.schemaFactory?
> The new admin UI doesn't understand that managed schemas are the default in
> 6.0
> -------------------------------------------------------------------------------
>
> Key: SOLR-8386
> URL: https://issues.apache.org/jira/browse/SOLR-8386
> Project: Solr
> Issue Type: Bug
> Components: UI
> Affects Versions: 6.0
> Reporter: Erick Erickson
>
> SOLR-8131 makes managed schema the default in Solr 6.0. So the "add field" &
> etc buttons aren't being shown in the schema link as they are in 5.x (5.4+).
> Note, _all_ the configsets in 5.5+ are managed, as they are in 6.x The
> difference is that you do not need to specify anything special in 6x.
> So whatever the key that determines whether the admin UI knows the schema is
> managed or not probably needs to be updated.
> [~upayavira] any hints here?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
