[jira] [Updated] (SOLR-9356) Highlight component added using Config API is not functional
[
https://issues.apache.org/jira/browse/SOLR-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex D updated SOLR-9356:
-
Component/s: config-api
> Highlight component added using Config API is not functional
>
>
> Key: SOLR-9356
> URL: https://issues.apache.org/jira/browse/SOLR-9356
> Project: Solr
> Issue Type: Sub-task
> Components: config-api, highlighter
>Affects Versions: 6.0.1
> Environment: SolrCloud on Windows with ZooKeeper 3.4.8
>Reporter: Alex D
>
> The configuration of a highlight component is not used when the component is
> added using the Config API. I used the following steps to reproduce the issue:
> 1) Add the highlight component on a request handler:
> on
> Email
> 0
> 2) Execute a search using the request handler. I can see the default
> configuration of the component returned in the results:
> "highlighting":{"a":{"Email":["roger2"]},"b":{
> "Email":"roger"]}
> 3) Add the highlight component using the Config API (see JSON below) & reload
> collection. No errors were returned by Solr when adding the component.
> 4) Execute the same search as step2 and we can see the format of the
> highlight is still using "em" instead of the new format from the Config API.
> Content of the post to the Config API:
> (Curl in a Windows' command prompt has some issues parsing the JSON so I used
> Fiddler to send it to Solr)
> {
>"add-searchcomponent":{
> "name":"highlight",
> "class":"solr.HighlightComponent",
> "":{
> "gap":{
> "default":"true",
> "name":"gap",
> "class":"solr.highlight.GapFragmenter",
> "defaults":{
>"hl.fragsize":100
> }
> },
> "regex":{
> "name":"regex",
> "class":"solr.highlight.RegexFragmenter",
> "defaults":{
>"hl.fragsize":70,
>"hl.regex.slop":0.5,
>"hl.regex.pattern":"[-\\w ,/\\n\\\"']{20,200}"
> }
> },
> "html":[
> {
>"default":"true",
>"name":"html",
>"class":"solr.highlight.HtmlFormatter",
>"defaults":{
> "hl.simple.pre":"pre-",
> "hl.simple.post":"-post"
>}
> },
> {
>"name":"html",
>"class":"solr.highlight.HtmlEncoder"
> }
> ],
> "simple":{
> "name":"simple",
> "class":"solr.highlight.SimpleFragListBuilder"
> },
> "single":{
> "name":"single",
> "class":"solr.highlight.SingleFragListBuilder"
> },
> "weighted":{
> "default":"true",
> "name":"weighted",
> "class":"solr.highlight.WeightedFragListBuilder"
> },
> "default":[
> {
>"default":"true",
>"name":"default",
>"class":"solr.highlight.ScoreOrderFragmentsBuilder"
> },
> {
>"default":"true",
>"name":"default",
>"class":"solr.highlight.SimpleBoundaryScanner",
>"defaults":{
> "hl.bs.maxScan":"10",
> "hl.bs.chars":".,!? \t\n\r"
>}
> }
> ],
> "colored":{
> "name":"colored",
> "class":"solr.highlight.ScoreOrderFragmentsBuilder",
> "defaults":{
>"hl.tag.pre":"pre-",
>"hl.tag.post":"-post"
> }
> },
> "breakIterator":{
> "name":"breakIterator",
> "class":"solr.highlight.BreakIteratorBoundaryScanner",
> "defaults":{
>"hl.bs.type":"WORD",
>"hl.bs.language":"en",
>"hl.bs.country":"US"
> }
> }
> }
>}
> }
--
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] [Created] (SOLR-9359) Listener added using Config API results in ClassCastException in the logs
Alex D created SOLR-9359:
Summary: Listener added using Config API results in
ClassCastException in the logs
Key: SOLR-9359
URL: https://issues.apache.org/jira/browse/SOLR-9359
Project: Solr
Issue Type: Sub-task
Components: config-api
Affects Versions: 6.0.1
Environment: SolrClound on Windows with ZooKeeper 3.4.8
Reporter: Alex D
Adding a listener using the Config API results in an exception in the logs even
if the call to the API was successful.
Command used to add the listener:
curl -k -u admin:admin https://solrserver:8443/solr/customer/config -H
'Content-type:application/json' -d '{ "add-listener":
{"event":"firstSearcher","class":"solr.QuerySenderListener","name":"f7fb2d87bea44464af2401cf33f42b69","queries":[{"q":"static
firstSearcher warming in solrconfig.xml"}]} }'
Result:
{
"responseHeader":{
"status":0,
"QTime":117},
"WARNING":"This response format is experimental. It is likely to change in
the future."}
In the Admin UI Logging section I can see the following error:
SolrCore null:java.lang.ClassCastException
The log files does not provide additional information.
--
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] [Updated] (SOLR-9354) ClusteringComponent added using Config API causes error when reloading the collection
[
https://issues.apache.org/jira/browse/SOLR-9354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex D updated SOLR-9354:
-
Description:
It is not possible to add a clustering search component when using the Config
API.
Command I used to add the clustering component:
curl -k -u admin:admin https://solrserver:8443/solr/customer/config -H
'Content-type:application/json' -d '{ "add-searchcomponent":
{"name":"clustering", "class": "solr.clustering.ClusteringComponent", "engine":
[{"name":"lingo","carrot.algorithm":
"org.carrot2.clustering.lingo.LingoClusteringAlgorithm"}, {"name":"stc",
"carrot.algorithm": "org.carrot2.clustering.stc.STCClusteringAlgorithm"}]} }'
Error I received from the curl command:
==
{
"responseHeader":{
"status":500,
"QTime":30026},
"errorMessages":["1 out of 2 the property overlay to be of version 7 within
30 seconds! Failed cores:
[https://solrserver:8443/solr/customer_shard1_replica1/]\n;],
"WARNING":"This response format is experimental. It is likely to change in
the future.",
"error":{
"metadata":[
"error-class","org.apache.solr.common.SolrException",
"root-error-class","org.apache.solr.common.SolrException"],
"msg":"1 out of 2 the property overlay to be of version 7 within 30
seconds! Failed cores:
[https://solrserver:8443/solr/customer_shard1_replica1/];,
"trace":"org.apache.solr.common.SolrException: 1 out of 2 the property
overlay to be of version 7 within 30 seconds! Failed cores:
[https://solrserver:8443/solr/customer_shard1_replica1/]\r\n\tat
org.apache.solr.handler.SolrConfigHandler.waitForAllReplicasState(SolrConfigHandler.java:710)\r\n\tat
org.apache.solr.handler.SolrConfigHandler.access$600(SolrConfigHandler.java:91)\r\n\tat
org.apache.solr.handler.SolrConfigHandler$Command.handleCommands(SolrConfigHandler.java:426)\r\n\tat
org.apache.solr.handler.SolrConfigHandler$Command.handlePOST(SolrConfigHandler.java:266)\r\n\tat
org.apache.solr.handler.SolrConfigHandler$Command.access$100(SolrConfigHandler.java:143)\r\n\tat
org.apache.solr.handler.SolrConfigHandler.handleRequestBody(SolrConfigHandler.java:121)\r\n\tat
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:155)\r\n\tat
org.apache.solr.core.SolrCore.execute(SolrCore.java:2053)\r\n\tat
org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:652)\r\n\tat
org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:460)\r\n\tat
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:229)\r\n\tat
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:184)\r\n\tat
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)\r\n\tat
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)\r\n\tat
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)\r\n\tat
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)\r\n\tat
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)\r\n\tat
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1160)\r\n\tat
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)\r\n\tat
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)\r\n\tat
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1092)\r\n\tat
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)\r\n\tat
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)\r\n\tat
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)\r\n\tat
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)\r\n\tat
org.eclipse.jetty.server.Server.handle(Server.java:518)\r\n\tat
org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308)\r\n\tat
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244)\r\n\tat
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)\r\n\tat
org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)\r\n\tat
org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:186)\r\n\tat
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)\r\n\tat
org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)\r\n\tat
org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)\r\n\tat
org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246)\r\n\tat
org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156)\r\n\tat
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)\r\n\tat
[jira] [Updated] (SOLR-9354) ClusteringComponent added using Config API causes error when reloading the collection
[
https://issues.apache.org/jira/browse/SOLR-9354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex D updated SOLR-9354:
-
Description:
It is not possible to add a clustering search component when using the Config
API.
Command I used to add the clustering component:
curl -k -u admin:admin https://solrserver:8443/solr/customer/config -H
'Content-type:application/json' -d '{ "add-searchcomponent":
{"name":"clustering", "class":"solr.clustering.ClusteringComponent","engine":[{
"name":"lingo",
"carrot.algorithm":"org.carrot2.clustering.lingo.LingoClusteringAlgorithm"}, {
"name":"stc",
"carrot.algorithm":"org.carrot2.clustering.stc.STCClusteringAlgorithm"}]} }'
Error I received from the curl command:
==
{
"responseHeader":{
"status":500,
"QTime":30026},
"errorMessages":["1 out of 2 the property overlay to be of version 7 within
30 seconds! Failed cores:
[https://solrserver:8443/solr/customer_shard1_replica1/]\n;],
"WARNING":"This response format is experimental. It is likely to change in
the future.",
"error":{
"metadata":[
"error-class","org.apache.solr.common.SolrException",
"root-error-class","org.apache.solr.common.SolrException"],
"msg":"1 out of 2 the property overlay to be of version 7 within 30
seconds! Failed cores:
[https://solrserver:8443/solr/customer_shard1_replica1/];,
"trace":"org.apache.solr.common.SolrException: 1 out of 2 the property
overlay to be of version 7 within 30 seconds! Failed cores:
[https://solrserver:8443/solr/customer_shard1_replica1/]\r\n\tat
org.apache.solr.handler.SolrConfigHandler.waitForAllReplicasState(SolrConfigHandler.java:710)\r\n\tat
org.apache.solr.handler.SolrConfigHandler.access$600(SolrConfigHandler.java:91)\r\n\tat
org.apache.solr.handler.SolrConfigHandler$Command.handleCommands(SolrConfigHandler.java:426)\r\n\tat
org.apache.solr.handler.SolrConfigHandler$Command.handlePOST(SolrConfigHandler.java:266)\r\n\tat
org.apache.solr.handler.SolrConfigHandler$Command.access$100(SolrConfigHandler.java:143)\r\n\tat
org.apache.solr.handler.SolrConfigHandler.handleRequestBody(SolrConfigHandler.java:121)\r\n\tat
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:155)\r\n\tat
org.apache.solr.core.SolrCore.execute(SolrCore.java:2053)\r\n\tat
org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:652)\r\n\tat
org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:460)\r\n\tat
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:229)\r\n\tat
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:184)\r\n\tat
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)\r\n\tat
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)\r\n\tat
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)\r\n\tat
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)\r\n\tat
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)\r\n\tat
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1160)\r\n\tat
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)\r\n\tat
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)\r\n\tat
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1092)\r\n\tat
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)\r\n\tat
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)\r\n\tat
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)\r\n\tat
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)\r\n\tat
org.eclipse.jetty.server.Server.handle(Server.java:518)\r\n\tat
org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308)\r\n\tat
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244)\r\n\tat
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)\r\n\tat
org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)\r\n\tat
org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:186)\r\n\tat
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)\r\n\tat
org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)\r\n\tat
org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)\r\n\tat
org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246)\r\n\tat
org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156)\r\n\tat
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)\r\n\tat
[jira] [Created] (SOLR-9356) Highlight component added using Config API is not functional
Alex D created SOLR-9356:
Summary: Highlight component added using Config API is not
functional
Key: SOLR-9356
URL: https://issues.apache.org/jira/browse/SOLR-9356
Project: Solr
Issue Type: Sub-task
Components: highlighter
Affects Versions: 6.0.1
Environment: SolrCloud on Windows with ZooKeeper 3.4.8
Reporter: Alex D
The configuration of a highlight component is not used when the component is
added using the Config API. I used the following steps to reproduce the issue:
1) Add the highlight component on a request handler:
on
Email
0
2) Execute a search using the request handler. I can see the default
configuration of the component returned in the results:
"highlighting":{"a":{"Email":["roger2"]},"b":{
"Email":"roger"]}
3) Add the highlight component using the Config API (see JSON below) & reload
collection. No errors were returned by Solr when adding the component.
4) Execute the same search as step2 and we can see the format of the highlight
is still using "em" instead of the new format from the Config API.
Content of the post to the Config API:
(Curl in a Windows' command prompt has some issues parsing the JSON so I used
Fiddler to send it to Solr)
{
"add-searchcomponent":{
"name":"highlight",
"class":"solr.HighlightComponent",
"":{
"gap":{
"default":"true",
"name":"gap",
"class":"solr.highlight.GapFragmenter",
"defaults":{
"hl.fragsize":100
}
},
"regex":{
"name":"regex",
"class":"solr.highlight.RegexFragmenter",
"defaults":{
"hl.fragsize":70,
"hl.regex.slop":0.5,
"hl.regex.pattern":"[-\\w ,/\\n\\\"']{20,200}"
}
},
"html":[
{
"default":"true",
"name":"html",
"class":"solr.highlight.HtmlFormatter",
"defaults":{
"hl.simple.pre":"pre-",
"hl.simple.post":"-post"
}
},
{
"name":"html",
"class":"solr.highlight.HtmlEncoder"
}
],
"simple":{
"name":"simple",
"class":"solr.highlight.SimpleFragListBuilder"
},
"single":{
"name":"single",
"class":"solr.highlight.SingleFragListBuilder"
},
"weighted":{
"default":"true",
"name":"weighted",
"class":"solr.highlight.WeightedFragListBuilder"
},
"default":[
{
"default":"true",
"name":"default",
"class":"solr.highlight.ScoreOrderFragmentsBuilder"
},
{
"default":"true",
"name":"default",
"class":"solr.highlight.SimpleBoundaryScanner",
"defaults":{
"hl.bs.maxScan":"10",
"hl.bs.chars":".,!? \t\n\r"
}
}
],
"colored":{
"name":"colored",
"class":"solr.highlight.ScoreOrderFragmentsBuilder",
"defaults":{
"hl.tag.pre":"pre-",
"hl.tag.post":"-post"
}
},
"breakIterator":{
"name":"breakIterator",
"class":"solr.highlight.BreakIteratorBoundaryScanner",
"defaults":{
"hl.bs.type":"WORD",
"hl.bs.language":"en",
"hl.bs.country":"US"
}
}
}
}
}
--
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] [Created] (SOLR-9354) ClusteringComponent added using Config API causes error when reloading the collection
Alex D created SOLR-9354:
Summary: ClusteringComponent added using Config API causes error
when reloading the collection
Key: SOLR-9354
URL: https://issues.apache.org/jira/browse/SOLR-9354
Project: Solr
Issue Type: Sub-task
Components: config-api, contrib - Clustering
Affects Versions: 6.0.1
Environment: SolrCloud on Windows with ZooKeeper 3.4.8
Reporter: Alex D
It is not possible to add a clustering search component when using the Config
API.
Command I used to add the clustering component:
curl -k -u admin:admin https://solrserver:8443/solr/customer/config -H
'Content-type:application/json' -d '{ "add-searchcomponent":
{"name":"clustering", "class":"solr.clustering.ClusteringComponent","engine":[{
"name":"lingo",
"carrot.algorithm":"org.carrot2.clustering.lingo.LingoClusteringAlgorithm"}, {
"name":"stc",
"carrot.algorithm":"org.carrot2.clustering.stc.STCClusteringAlgorithm"}]} }'
Error I received from the curl command:
{
"responseHeader":{
"status":500,
"QTime":30026},
"errorMessages":["1 out of 2 the property overlay to be of version 7 within
30 seconds! Failed cores:
[https://solrserver:8443/solr/customer_shard1_replica1/]\n;],
"WARNING":"This response format is experimental. It is likely to change in
the future.",
"error":{
"metadata":[
"error-class","org.apache.solr.common.SolrException",
"root-error-class","org.apache.solr.common.SolrException"],
"msg":"1 out of 2 the property overlay to be of version 7 within 30
seconds! Failed cores:
[https://solrserver:8443/solr/customer_shard1_replica1/];,
"trace":"org.apache.solr.common.SolrException: 1 out of 2 the property
overlay to be of version 7 within 30 seconds! Failed cores:
[https://solrserver:8443/solr/customer_shard1_replica1/]\r\n\tat
org.apache.solr.handler.SolrConfigHandler.waitForAllReplicasState(SolrConfigHandler.java:710)\r\n\tat
org.apache.solr.handler.SolrConfigHandler.access$600(SolrConfigHandler.java:91)\r\n\tat
org.apache.solr.handler.SolrConfigHandler$Command.handleCommands(SolrConfigHandler.java:426)\r\n\tat
org.apache.solr.handler.SolrConfigHandler$Command.handlePOST(SolrConfigHandler.java:266)\r\n\tat
org.apache.solr.handler.SolrConfigHandler$Command.access$100(SolrConfigHandler.java:143)\r\n\tat
org.apache.solr.handler.SolrConfigHandler.handleRequestBody(SolrConfigHandler.java:121)\r\n\tat
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:155)\r\n\tat
org.apache.solr.core.SolrCore.execute(SolrCore.java:2053)\r\n\tat
org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:652)\r\n\tat
org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:460)\r\n\tat
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:229)\r\n\tat
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:184)\r\n\tat
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)\r\n\tat
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)\r\n\tat
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)\r\n\tat
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)\r\n\tat
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)\r\n\tat
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1160)\r\n\tat
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)\r\n\tat
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)\r\n\tat
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1092)\r\n\tat
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)\r\n\tat
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)\r\n\tat
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)\r\n\tat
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)\r\n\tat
org.eclipse.jetty.server.Server.handle(Server.java:518)\r\n\tat
org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308)\r\n\tat
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244)\r\n\tat
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)\r\n\tat
org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)\r\n\tat
org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:186)\r\n\tat
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)\r\n\tat
org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)\r\n\tat
org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)\r\n\tat
[jira] [Commented] (SOLR-9197) Audit all solrconfig components and ensure that they work with the Config APIs
[
https://issues.apache.org/jira/browse/SOLR-9197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15397851#comment-15397851
]
Alex D commented on SOLR-9197:
--
I found another component that do not work when using the Config API:
ClusteringComponent.
The error I got was : "org.apache.solr.common.SolrException:
java.util.ArrayList cannot be cast to org.apache.solr.common.util.NamedList".
I was wondering if I should keep adding comments to this Jira when I find
components that are not working when using the Config API.
> Audit all solrconfig components and ensure that they work with the Config APIs
> --
>
> Key: SOLR-9197
> URL: https://issues.apache.org/jira/browse/SOLR-9197
> Project: Solr
> Issue Type: Bug
>Reporter: Noble Paul
>Assignee: Noble Paul
>
> Components assume that the configuration is read from {{solrconfig.xml}} and
> all values are NamedList. Config APIs use and store JSON and the syntax is
> different. Components should work with both syntax.
--
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-9197) Audit all solrconfig components and ensure that they work with the Config APIs
[
https://issues.apache.org/jira/browse/SOLR-9197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385779#comment-15385779
]
Alex D commented on SOLR-9197:
--
My issue may be related to this Jira.
I tried adding a highlight search component using the Config API and it is not
picked up by Solr. I can see my new highlight search component when using
Solr's "/solr//config" however the request handler is using the
default highlighting values instead of the ones I specified.
I can post the relevant configuration if it helps.
> Audit all solrconfig components and ensure that they work with the Config APIs
> --
>
> Key: SOLR-9197
> URL: https://issues.apache.org/jira/browse/SOLR-9197
> Project: Solr
> Issue Type: Bug
>Reporter: Noble Paul
>Assignee: Noble Paul
>
> Components assume that the configuration is read from {{solrconfig.xml}} and
> all values are NamedList. Config APIs use and store JSON and the syntax is
> different. Components should work with both syntax.
--
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-9188) BlockUnknown property makes inter-node communication impossible
[
https://issues.apache.org/jira/browse/SOLR-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366524#comment-15366524
]
Alex D commented on SOLR-9188:
--
On my development workstation (windows) I was able to workaround the issue by
editing solr.in.cmd and changing SOLR_HOST to include a username & password.
e.g.:
set SOLR_HOST=username:passw...@mysolrhost.com
> BlockUnknown property makes inter-node communication impossible
> ---
>
> Key: SOLR-9188
> URL: https://issues.apache.org/jira/browse/SOLR-9188
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
>Affects Versions: 6.0
>Reporter: Piotr Tempes
>
> When I setup my solr cloud without blockUnknown property it works as
> expected. When I want to block non authenticated requests I get following
> stacktrace during startup:
> {code}
> 2016-06-06 05:49:16.360 INFO
> (coreZkRegister-1-thread-1-processing-n:172.30.92.66:8983_solr
> x:testowa_shard1_replica3 s:shard1 c:testowa r:core_node1) [c:testowa
> s:shard1 r:core_node1 x:testowa_shard1_replica3]
> o.a.s.c.ShardLeaderElectionContext Enough replicas found to continue.
> 2016-06-06 05:49:16.360 INFO
> (coreZkRegister-1-thread-1-processing-n:172.30.92.66:8983_solr
> x:testowa_shard1_replica3 s:shard1 c:testowa r:core_node1) [c:testowa
> s:shard1 r:core_node1 x:testowa_shard1_replica3]
> o.a.s.c.ShardLeaderElectionContext I may be the new leader - try and sync
> 2016-06-06 05:49:16.361 INFO
> (coreZkRegister-1-thread-1-processing-n:172.30.92.66:8983_solr
> x:testowa_shard1_replica3 s:shard1 c:testowa r:core_node1) [c:testowa
> s:shard1 r:core_node1 x:testowa_shard1_replica3] o.a.s.c.SyncStrategy Sync
> replicas to https://172.30.92.66:8983/solr/testowa_shard1_replica3/
> 2016-06-06 05:49:16.364 INFO
> (coreZkRegister-1-thread-1-processing-n:172.30.92.66:8983_solr
> x:testowa_shard1_replica3 s:shard1 c:testowa r:core_node1) [c:testowa
> s:shard1 r:core_node1 x:testowa_shard1_replica3] o.a.s.u.PeerSync PeerSync:
> core=testowa_shard1_replica3 url=https://172.30.92.66:8983/solr START
> replicas=[https://172.30.182.43:8983/solr/testowa_shard1_replica1/,
> https://172.30.182.44:8983/solr/testowa_shard1_replica2/] nUpdates=100
> 2016-06-06 05:49:16.365 INFO
> (OverseerStateUpdate-240112591792046141-172.30.92.66:8983_solr-n_000150)
> [ ] o.a.s.c.o.ReplicaMutator Update state numShards=1 message={
> "core":"retailers_shard1_replica1",
> "core_node_name":"core_node1",
> "roles":null,
> "base_url":"https://172.30.182.44:8983/solr;,
> "node_name":"172.30.182.44:8983_solr",
> "numShards":"1",
> "state":"active",
> "shard":"shard1",
> "collection":"retailers",
> "operation":"state"}
> 2016-06-06 05:49:16.481 INFO
> (OverseerStateUpdate-240112591792046141-172.30.92.66:8983_solr-n_000150)
> [ ] o.a.s.c.o.ZkStateWriter going to update_collection
> /collections/retailers/state.json version: 89
> 2016-06-06 05:49:17.758 WARN
> (coreZkRegister-1-thread-1-processing-n:172.30.92.66:8983_solr
> x:testowa_shard1_replica3 s:shard1 c:testowa r:core_node1) [c:testowa
> s:shard1 r:core_node1 x:testowa_shard1_replica3] o.a.s.u.PeerSync PeerSync:
> core=testowa_shard1_replica3 url=https://172.30.92.66:8983/solr exception
> talking to https://172.30.182.44:8983/solr/testowa_shard1_replica2/, failed
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error
> from server at https://172.30.182.44:8983/solr/testowa_shard1_replica2:
> Expected mime type application/octet-stream but got text/html.
>
>
> Error 401 Unauthorized request, Response code: 401
>
> HTTP ERROR 401
> Problem accessing /solr/testowa_shard1_replica2/get. Reason:
> Unauthorized request, Response code: 401
>
>
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:545)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:241)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:230)
> at org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1219)
> at
> org.apache.solr.handler.component.HttpShardHandler$1.call(HttpShardHandler.java:198)
> at
> org.apache.solr.handler.component.HttpShardHandler$1.call(HttpShardHandler.java:163)
> at java.util.concurrent.FutureTask.run(FutureTask.java:277)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:522)
> at java.util.concurrent.FutureTask.run(FutureTask.java:277)
> at
> org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:229)
> at
> org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor$$Lambda$3.C403EBB0.run(Unknown
> Source)
> at
>
[jira] [Comment Edited] (SOLR-9154) Config API does not work when adding a component with DirectSolrSpellChecker
[
https://issues.apache.org/jira/browse/SOLR-9154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15355332#comment-15355332
]
Alex D edited comment on SOLR-9154 at 6/29/16 3:24 PM:
---
Would it be possible to convert the config variable to a SolrParams (e.g.:
using SolrParams.toSolrParams)? This way you could use get* methods instead of
parsing the string yourself.
was (Author: alexandre.drouin):
Would it be possible to convert the config variable to a SolrParams (e.g.:
using SolrParams.toSolrParams)? This way you could use getField* methods
instead of parsing the string yourself.
> Config API does not work when adding a component with DirectSolrSpellChecker
>
>
> Key: SOLR-9154
> URL: https://issues.apache.org/jira/browse/SOLR-9154
> Project: Solr
> Issue Type: Bug
> Components: config-api, spellchecker
>Reporter: Anshum Gupta
>Assignee: Anshum Gupta
> Fix For: 6.2, master (7.0)
>
> Attachments: SOLR-9154.patch
>
>
> When trying to add a DirectSolrSpellchecker using the Config API (JSON),
> there seems to be a loss of information w.r.t the param types. The accuracy
> field, only in this specific case needs to be defined as a float it seems.
> While this is possible when updating the solrconfig,xml directly, the field
> type (float) can not be specified using JSON.
> Here are the steps to reproduce this issue:
> {code}
> #Bootstrapping
> bin/solr start -c
> bin/solr create -c foo
> bin/post -c foo example/exampledocs/books.csv
> #Add spell checker - This would hang and the logs contain recurring
> exceptions as mentioned below
> curl http://localhost:8983/solr/foo/config -H 'Content-type:application/json'
> -d '{"update-searchcomponent": {"name":"spellcheck",
> "class":"solr.SpellCheckComponent", "spellchecker":[ {
> "name":"text_index_dictionary", "field":"text",
> "classname":"solr.DirectSolrSpellChecker",
> "distanceMeasure":"org.apache.lucene.search.spell.LevensteinDistance",
> "accuracy":0.5, "maxEdits":2, "minPrefix":1, "maxInspections":5,
> "minQueryLength":4, "maxQueryFrequency":0.001,
> "thresholdTokenFrequency":0.01}]}}'
> {code}
> Log:
> {code}
> 2016-05-24 04:08:44.371 ERROR (SolrConfigHandler-refreshconf) [c:foo s:shard1
> r:core_node1 x:foo_shard1_replica1] o.a.s.h.SolrConfigHandler Unable to
> refresh conf
> org.apache.solr.common.SolrException: Unable to reload core
> [foo_shard1_replica1]
> at org.apache.solr.core.CoreContainer.reload(CoreContainer.java:944)
> at
> org.apache.solr.core.SolrCore.lambda$getConfListener$7(SolrCore.java:2510)
> at
> org.apache.solr.handler.SolrConfigHandler$Command$1.run(SolrConfigHandler.java:218)
> Caused by: org.apache.solr.common.SolrException: java.lang.Double cannot be
> cast to java.lang.Float
> at org.apache.solr.core.SolrCore.(SolrCore.java:773)
> at org.apache.solr.core.SolrCore.reload(SolrCore.java:462)
> at org.apache.solr.core.CoreContainer.reload(CoreContainer.java:938)
> {code}
--
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-9154) Config API does not work when adding a component with DirectSolrSpellChecker
[
https://issues.apache.org/jira/browse/SOLR-9154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15355332#comment-15355332
]
Alex D commented on SOLR-9154:
--
Would it be possible to convert the config variable to a SolrParams (e.g.:
using SolrParams.toSolrParams)? This way you could use getField* methods
instead of parsing the string yourself.
> Config API does not work when adding a component with DirectSolrSpellChecker
>
>
> Key: SOLR-9154
> URL: https://issues.apache.org/jira/browse/SOLR-9154
> Project: Solr
> Issue Type: Bug
> Components: config-api, spellchecker
>Reporter: Anshum Gupta
>Assignee: Anshum Gupta
> Fix For: 6.2, master (7.0)
>
> Attachments: SOLR-9154.patch
>
>
> When trying to add a DirectSolrSpellchecker using the Config API (JSON),
> there seems to be a loss of information w.r.t the param types. The accuracy
> field, only in this specific case needs to be defined as a float it seems.
> While this is possible when updating the solrconfig,xml directly, the field
> type (float) can not be specified using JSON.
> Here are the steps to reproduce this issue:
> {code}
> #Bootstrapping
> bin/solr start -c
> bin/solr create -c foo
> bin/post -c foo example/exampledocs/books.csv
> #Add spell checker - This would hang and the logs contain recurring
> exceptions as mentioned below
> curl http://localhost:8983/solr/foo/config -H 'Content-type:application/json'
> -d '{"update-searchcomponent": {"name":"spellcheck",
> "class":"solr.SpellCheckComponent", "spellchecker":[ {
> "name":"text_index_dictionary", "field":"text",
> "classname":"solr.DirectSolrSpellChecker",
> "distanceMeasure":"org.apache.lucene.search.spell.LevensteinDistance",
> "accuracy":0.5, "maxEdits":2, "minPrefix":1, "maxInspections":5,
> "minQueryLength":4, "maxQueryFrequency":0.001,
> "thresholdTokenFrequency":0.01}]}}'
> {code}
> Log:
> {code}
> 2016-05-24 04:08:44.371 ERROR (SolrConfigHandler-refreshconf) [c:foo s:shard1
> r:core_node1 x:foo_shard1_replica1] o.a.s.h.SolrConfigHandler Unable to
> refresh conf
> org.apache.solr.common.SolrException: Unable to reload core
> [foo_shard1_replica1]
> at org.apache.solr.core.CoreContainer.reload(CoreContainer.java:944)
> at
> org.apache.solr.core.SolrCore.lambda$getConfListener$7(SolrCore.java:2510)
> at
> org.apache.solr.handler.SolrConfigHandler$Command$1.run(SolrConfigHandler.java:218)
> Caused by: org.apache.solr.common.SolrException: java.lang.Double cannot be
> cast to java.lang.Float
> at org.apache.solr.core.SolrCore.(SolrCore.java:773)
> at org.apache.solr.core.SolrCore.reload(SolrCore.java:462)
> at org.apache.solr.core.CoreContainer.reload(CoreContainer.java:938)
> {code}
--
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
