[
https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924513#comment-15924513
]
Hoss Man commented on SOLR-8045:
--------------------------------
bq. can you make it clearer ? v2 api is not yet released. So where is the
backcompat problem coming from
Huh? ... what you mean by "v2 api is not yet released" ... there seems to be
plenty of v2 API related code released in 6.4.0 ??
I'm talking about the way this issue changed the path that users (apparently)
need to specify in their {{registerPath}} declarations -- regardless of whether
they do that manually in solrconfig.xml, or via the API.
specifically these types of change in the branch_6x commits...
https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=blobdiff;f=solr/server/solr/configsets/sample_techproducts_configs/conf/solrconfig.xml;h=3dda6629610b45c57affef2e4c0b4256ae3a7d91;hp=a722176896139d02218bcc9d4fe282ca372ae69c;hb=89baa4f;hpb=8c5ea32bb9f2d9d8af98162e1e19c9559c8c602d
{noformat}
- <requestHandler name="/query" class="solr.SearchHandler"
registerPath="/,/v2">
+ <requestHandler name="/query" class="solr.SearchHandler"
registerPath="/solr,/v2">
{noformat}
https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=blobdiff;f=solr/core/src/test/org/apache/solr/core/TestDynamicLoading.java;h=306b4b2105dff177f7c6d700c2e9fd55b7877992;hp=8479ae4f48f2e2393a1cecc61cf9f5e6d28e5789;hb=89baa4f;hpb=8c5ea32bb9f2d9d8af98162e1e19c9559c8c602d
{noformat}
- "'create-requesthandler' : { 'name' : '/test1', 'class':
'org.apache.solr.core.BlobStoreTestRequestHandler' ,registerPath: '/,/v2',
'runtimeLib' : true }\n" +
+ "'create-requesthandler' : { 'name' : '/test1', 'class':
'org.apache.solr.core.BlobStoreTestRequestHandler' ,registerPath: '/solr,/v2',
'runtimeLib' : true }\n" +
{noformat}
...etc.
If i'm understanding those changes correctly, even if a use doesn't care about
the v2 api at all, won't their request handlers stop working unless they have
this {{registerPath=/solr}} change?
(or is {{registerPath}} a completely new concept that won't affect existing
users if unspecified when upgrading existing configs?)
> Deploy V2 API at /v2 instead of /solr/v2
> ----------------------------------------
>
> Key: SOLR-8045
> URL: https://issues.apache.org/jira/browse/SOLR-8045
> Project: Solr
> Issue Type: Wish
> Reporter: Noble Paul
> Assignee: Cao Manh Dat
> Priority: Blocker
> Fix For: 6.5
>
> Attachments: SOLR-8045.patch, SOLR-8045.patch, SOLR-8045.patch,
> SOLR-8045.patch, SOLR-8045.patch, SOLR-8045.patch, SOLR-8045.patch
>
>
> This does not mean that the path to access Solr will be changed. All paths
> will remain as is and would behave exactly the same
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
