[jira] [Commented] (SOLR-8045) Deploy V2 API at /v2 instead of /solr/v2
[ https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936334#comment-15936334 ] Alexandre Rafalovitch commented on SOLR-8045: - Can be closed? It is now in 6.5rc1. > 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
[jira] [Commented] (SOLR-8045) Deploy V2 API at /v2 instead of /solr/v2
[ https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925711#comment-15925711 ] ASF subversion and git services commented on SOLR-8045: --- Commit 124b50581041d6b2b3e68aa37a26e66aceb2abf1 in lucene-solr's branch refs/heads/master from [~noble.paul] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=124b505 ] SOLR-8045: SerachHandler to override the registerV2() and remove registerPath from sample solrconfig.xml > 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
[jira] [Commented] (SOLR-8045) Deploy V2 API at /v2 instead of /solr/v2
[ https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925708#comment-15925708 ] ASF subversion and git services commented on SOLR-8045: --- Commit b9f371e1e735554722ec2153b60593cded547c4c in lucene-solr's branch refs/heads/branch_6x from [~noble.paul] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=b9f371e ] SOLR-8045: SerachHandler to override the registerV2() and remove registerPath from sample solrconfig.xml > 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
[jira] [Commented] (SOLR-8045) Deploy V2 API at /v2 instead of /solr/v2
[
https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925704#comment-15925704
]
Noble Paul commented on SOLR-8045:
--
The tests use the {{DumpRequestHandler}} which does not automatically support
the {{/v2}} path, so it is forced to be registered at the {{/v2}} using the
{{registerPath}} attribute.
bq. but it's not clear to be that the default effective value . (of
registerPath when unspecified by a user)
the default value of {{registerPath}} is empty. If it is empty, the framework
asks the request handler where to deploy it. By default, all components
register at {{/solr}} and not register at {{/v2}}. However components can
override the {{registerV2()}} methode and return true to signal that it should
be registered at {{/v2}}
I can effectively remove that entry from {{solrconfig.xml}} by overriding that
method and return true.
> 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
[jira] [Commented] (SOLR-8045) Deploy V2 API at /v2 instead of /solr/v2
[
https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924720#comment-15924720
]
Hoss Man commented on SOLR-8045:
bq. 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 ??
whoops ... my mistake. I must not have been been looking at the correct branch.
the crux of my question is still about the effective default behavior of this
{{registerPath}} option ... because i see Dat's commit changing _existing_
tests & configs to use {{/solr} instead of {{/}} -- but it's not clear to be
that the _default_ *effective* value (of {{registerPath}} when unspecified by a
user) has been changed to {{/solr}} ... or if the default effective value is
impacted by this issue at all.
Or to put it in a (broader) nutshell: are we 100% certain existing 6.4 users
who upgrade their solr instances to branch_6x, w/o making any config changes,
are unaffected by this change?
> 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
[jira] [Commented] (SOLR-8045) Deploy V2 API at /v2 instead of /solr/v2
[
https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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}
-
+
{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
[jira] [Commented] (SOLR-8045) Deploy V2 API at /v2 instead of /solr/v2
[ https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923383#comment-15923383 ] ASF subversion and git services commented on SOLR-8045: --- Commit 464722a0a8ca1811d922e346d219d08676a12e65 in lucene-solr's branch refs/heads/branch_6x from [~caomanhdat] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=464722a ] SOLR-8045: Fix smokeTestRelease.py from precommit > 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
[jira] [Commented] (SOLR-8045) Deploy V2 API at /v2 instead of /solr/v2
[ https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923377#comment-15923377 ] ASF subversion and git services commented on SOLR-8045: --- Commit faeb1fe8c16f9e02aa5c3bba295bc24325b94a07 in lucene-solr's branch refs/heads/master from [~caomanhdat] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=faeb1fe ] SOLR-8045: Fix smokeTestRelease.py from precommit > 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
[jira] [Commented] (SOLR-8045) Deploy V2 API at /v2 instead of /solr/v2
[ https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923358#comment-15923358 ] Noble Paul commented on SOLR-8045: -- bq.i'm concerned about this change being backported to 6x, since (IIUC) it means users have to change any existing requestHandler declarations they have that already use a registerPath attribute. can you make it clearer ? v2 api is not yet released. So where is the backcompat problem coming from > 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
[jira] [Commented] (SOLR-8045) Deploy V2 API at /v2 instead of /solr/v2
[
https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923176#comment-15923176
]
Hoss Man commented on SOLR-8045:
in addition to the smoketester failures -- i'm concerned about this change
being backported to 6x, since (IIUC) it means users have to change any existing
{{requestHandler}} declarations they have that already use a {{registerPath}}
attribute.
(This is an assumption on my part based on the fact that the commit seems to
have included a change to every existing {{registerPath}} declaration -- either
in a sample (or test) config, and in any test that called
{{'add-requesthandler'}})
that type of change may be fine for 7.0, with an adequate upgrade instruction,
but I worry about this breaking stuff for people who upgrade from 6.x to 6.5
w/o changing their 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
> 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
[jira] [Commented] (SOLR-8045) Deploy V2 API at /v2 instead of /solr/v2
[
https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906292#comment-15906292
]
Steve Rowe commented on SOLR-8045:
--
Same (looking) failure on master
[https://builds.apache.org/job/Lucene-Solr-SmokeRelease-master/723/]:
{noformat}
[smoker] Test Solr...
[...]
[smoker] Solr techproducts example launched successfully. Direct your Web
browser to http://localhost:8983/solr to visit the Solr Admin UI
[smoker] test utf8...
[smoker] run query...
[smoker] FAILED: response is:
[smoker]
{"responseHeader":{"status":0,"QTime":2},"initFailures":{},"status":{"techproducts":{"name":"techproducts","instanceDir":"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/lucene/build/smokeTestRelease/tmp/unpack/solr-7.0.0-java8/example/techproducts/solr/techproducts","dataDir":"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/lucene/build/smokeTestRelease/tmp/unpack/solr-7.0.0-java8/example/techproducts/solr/techproducts/data/","config":"solrconfig.xml","schema":"managed-schema","startTime":"2017-03-11T18:52:09.695Z","uptime":1178,"index":{"numDocs":32,"maxDoc":32,"deletedDocs":0,"indexHeapUsageBytes":-1,"version":6,"segmentCount":1,"current":true,"hasDeletions":false,"directory":"org.apache.lucene.store.NRTCachingDirectory:NRTCachingDirectory(MMapDirectory@/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/lucene/build/smokeTestRelease/tmp/unpack/solr-7.0.0-java8/example/techproducts/solr/techproducts/data/index
lockFactory=org.apache.lucene.store.NativeFSLockFactory@45968d2f;
maxCacheMB=48.0
maxMergeSizeMB=4.0)","segmentsFile":"segments_2","segmentsFileSizeInBytes":169,"userData":{"commitTimeMSec":"1489258330575"},"lastModified":"2017-03-11T18:52:10.575Z","sizeInBytes":28881,"size":"28.2
KB"
[smoker]
[smoker] stop server using: bin/solr stop -p 8983
[smoker] Sending stop command to Solr running on port 8983 ... waiting up to
180 seconds to allow Jetty process 5742 to stop gracefully.
[smoker] Traceback (most recent call last):
[smoker] File
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/dev-tools/scripts/smokeTestRelease.py",
line 1478, in
[smoker] main()
[smoker] File
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/dev-tools/scripts/smokeTestRelease.py",
line 1422, in main
[smoker] smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir,
c.is_signed, ' '.join(c.test_args))
[smoker] File
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/dev-tools/scripts/smokeTestRelease.py",
line 1466, in smokeTest
[smoker] unpackAndVerify(java, 'solr', tmpDir, artifact, gitRevision,
version, testArgs, baseURL)
[smoker] File
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/dev-tools/scripts/smokeTestRelease.py",
line 622, in unpackAndVerify
[smoker] verifyUnpacked(java, project, artifact, unpackPath, gitRevision,
version, testArgs, tmpDir, baseURL)
[smoker] File
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/dev-tools/scripts/smokeTestRelease.py",
line 760, in verifyUnpacked
[smoker] testSolrExample(java8UnpackPath, java.java8_home, False)
[smoker] File
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/dev-tools/scripts/smokeTestRelease.py",
line 861, in testSolrExample
[smoker] raise RuntimeError('query api v2 on solr example instance
failed')
[smoker] RuntimeError: query api v2 on solr example instance failed
[smoker] [|] [/] [-] [\]
{noformat}
> 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
> 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
[jira] [Commented] (SOLR-8045) Deploy V2 API at /v2 instead of /solr/v2
[
https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906282#comment-15906282
]
Steve Rowe commented on SOLR-8045:
--
ASF Jenkins has a smoke tester failure after this issue's branch_6x commit
[https://builds.apache.org/job/Lucene-Solr-SmokeRelease-6.x/283/] - when I run
{{ant nightly-smoke}} without a seed on current branch_6x, I see the same
failure:
{noformat}
Checking out Revision 89baa4fd43477c3b0be59e81299b651d70b3c128
(refs/remotes/origin/branch_6x)
[...]
[smoker] Test Solr...
[...]
[smoker] Solr techproducts example launched successfully. Direct your Web
browser to http://localhost:8983/solr to visit the Solr Admin UI
[smoker] test utf8...
[smoker] run query...
[smoker] FAILED: response is:
[smoker]
{"responseHeader":{"status":0,"QTime":2},"initFailures":{},"status":{"techproducts":{"name":"techproducts","instanceDir":"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-6.x/lucene/build/smokeTestRelease/tmp/unpack/solr-6.5.0-java8/example/techproducts/solr/techproducts","dataDir":"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-6.x/lucene/build/smokeTestRelease/tmp/unpack/solr-6.5.0-java8/example/techproducts/solr/techproducts/data/","config":"solrconfig.xml","schema":"managed-schema","startTime":"2017-03-11T14:53:39.348Z","uptime":1183,"index":{"numDocs":32,"maxDoc":32,"deletedDocs":0,"indexHeapUsageBytes":-1,"version":6,"segmentCount":1,"current":true,"hasDeletions":false,"directory":"org.apache.lucene.store.NRTCachingDirectory:NRTCachingDirectory(MMapDirectory@/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-6.x/lucene/build/smokeTestRelease/tmp/unpack/solr-6.5.0-java8/example/techproducts/solr/techproducts/data/index
lockFactory=org.apache.lucene.store.NativeFSLockFactory@2a09960c;
maxCacheMB=48.0
maxMergeSizeMB=4.0)","segmentsFile":"segments_2","segmentsFileSizeInBytes":165,"userData":{"commitTimeMSec":"1489244020126"},"lastModified":"2017-03-11T14:53:40.126Z","sizeInBytes":28411,"size":"27.75
KB"
[smoker]
[smoker] stop server using: bin/solr stop -p 8983
[smoker] Sending stop command to Solr running on port 8983 ... waiting up to
180 seconds to allow Jetty process 15932 to stop gracefully.
[smoker] Traceback (most recent call last):
[smoker] File
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-6.x/dev-tools/scripts/smokeTestRelease.py",
line 1476, in
[smoker] main()
[smoker] File
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-6.x/dev-tools/scripts/smokeTestRelease.py",
line 1420, in main
[smoker] smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir,
c.is_signed, ' '.join(c.test_args))
[smoker] File
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-6.x/dev-tools/scripts/smokeTestRelease.py",
line 1464, in smokeTest
[smoker] unpackAndVerify(java, 'solr', tmpDir, artifact, gitRevision,
version, testArgs, baseURL)
[smoker] File
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-6.x/dev-tools/scripts/smokeTestRelease.py",
line 622, in unpackAndVerify
[smoker] verifyUnpacked(java, project, artifact, unpackPath,
gitRevision, version, testArgs, tmpDir, baseURL)
[smoker] File
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-6.x/dev-tools/scripts/smokeTestRelease.py",
line 760, in verifyUnpacked
[smoker] testSolrExample(java8UnpackPath, java.java8_home, False)
[smoker] File
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-6.x/dev-tools/scripts/smokeTestRelease.py",
line 861, in testSolrExample
[smoker] raise RuntimeError('query api v2 on solr example instance
failed')
[smoker] RuntimeError: query api v2 on solr example instance failed
[smoker] [|] [/] [-] [\]
{noformat}
When I run {{ant nightly-smoke}} on branch_6x at {{8c5ea32}}, the commit just
before this issue was committed to branch_6x, I don't see this failure.
> 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
> 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
[jira] [Commented] (SOLR-8045) Deploy V2 API at /v2 instead of /solr/v2
[ https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906046#comment-15906046 ] ASF subversion and git services commented on SOLR-8045: --- Commit 89baa4fd43477c3b0be59e81299b651d70b3c128 in lucene-solr's branch refs/heads/branch_6x from [~caomanhdat] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=89baa4f ] SOLR-8045: Deploy V2 API at /v2 instead of /solr/v2 > 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 > 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
[jira] [Commented] (SOLR-8045) Deploy V2 API at /v2 instead of /solr/v2
[ https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906044#comment-15906044 ] ASF subversion and git services commented on SOLR-8045: --- Commit 0fb386a864ff5b7d32af3bef3f7eeca4d009acc1 in lucene-solr's branch refs/heads/master from [~caomanhdat] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=0fb386a ] SOLR-8045: Deploy V2 API at /v2 instead of /solr/v2 > 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 > Fix For: 6.0 > > 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
