[ 
https://issues.apache.org/jira/browse/SOLR-10035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840454#comment-15840454
 ] 

Jan Høydahl commented on SOLR-10035:
------------------------------------

bq. So I think that the least confusing option at this point would be to add a 
very clear note in CHANGES and keep the new names (and avoid breaking 
back-compat in the future!) Keeping both new and old names is an option, too, 
but it may be more confusing in the UI / JMX.

Or some middle ground. Expose both old and new for the rest of 6.x and add a 
{{-Dsolr.mbeans.useOnlyNewNaming=true}} flag which removes the old names with a 
warning in release notes that this breaks back compat to gain less confusing 
GUI output. Anyway most users will not even notice, except those that use a 
monitoring solution which suddenly breaks. Then again, very few have had the 
chance to upgrade to 6.4 yet

> Admin UI cannot find dataimport handlers
> ----------------------------------------
>
>                 Key: SOLR-10035
>                 URL: https://issues.apache.org/jira/browse/SOLR-10035
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: UI
>    Affects Versions: 6.4.0
>            Reporter: Shawn Heisey
>            Assignee: Andrzej Bialecki 
>              Labels: regression
>             Fix For: master (7.0), 6.4.1
>
>
> The 6.4.0 version of Solr has a problem with the Dataimport tab in the admin 
> UI.  It will say "Sorry, no dataimport-handler defined" when trying to access 
> that tab.
> The root cause of the problem is a change in the /admin/mbeans handler, by 
> SOLR-9947.  The section of the output where defined dataimport handlers are 
> listed was changed from QUERYHANDLER to QUERY.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to