[jira] [Commented] (SOLR-9935) When hl.method=unified add support for hl.fragsize param
[
https://issues.apache.org/jira/browse/SOLR-9935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16398647#comment-16398647
]
Mohsen commented on SOLR-9935:
--
Is this really resolved as of Solr 6.4? I tested with both Solr 6.4.1 and Solr
7.1 installations and none of them recognize hl.fragsize when unified method is
used.
> When hl.method=unified add support for hl.fragsize param
>
>
> Key: SOLR-9935
> URL: https://issues.apache.org/jira/browse/SOLR-9935
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: highlighter
>Reporter: David Smiley
>Assignee: David Smiley
>Priority: Major
> Fix For: 6.4
>
> Attachments: SOLR_9935_UH_fragsize.patch, SOLR_9935_UH_fragsize.patch
>
>
> In LUCENE-7620 the UnifiedHighlighter is getting a BreakIterator that allows
> it to support the equivalent of Solr's {{hl.fragsize}}. So lets support this
> on the Solr side.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6239) HttpSolrServer: connection still allocated
[
https://issues.apache.org/jira/browse/SOLR-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14958496#comment-14958496
]
Mohsen commented on SOLR-6239:
--
Shawn, sorry for my confusing comment.
I'm using Solr (single instance, no cloud) in a few rather high traffic news
websites for some years (from Solr 1.4 to 5.2). Recently when I was trying to
add basic HTTP auth to a Solr client, I encountered this SolrJ / HC error. The
code I was using is [here|https://gist.github.com/maddingo/2487775], but
slightly modified to fix the issue mentioned in this report. I didn't see this
error yet in any of my previous apps, until I added basic authentication to
HttpSolrClient(/Server).
My comment was actually misleading because it should go under [this
post|https://gist.github.com/maddingo/2487775], not here.
Thanks.
> HttpSolrServer: connection still allocated
> --
>
> Key: SOLR-6239
> URL: https://issues.apache.org/jira/browse/SOLR-6239
> Project: Solr
> Issue Type: Bug
> Components: clients - java
>Affects Versions: 4.9
>Reporter: Sergio Fernández
>Priority: Minor
>
> In scenarios where concurrency is aggressive, this exception could easily
> appear:
> {quote}
> org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Invalid
> use of BasicClientConnManager: connection still allocated.
> Make sure to release the connection before allocating another one.
> at
> org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:554)
> ~[solr-solrj-4.9.0.jar:4.9.0 1604085 - rmuir - 2014-06-20 06:34:04]
> at
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
> ~[solr-solrj-4.9.0.jar:4.9.0 1604085 - rmuir - 2014-06-20 06:34:04]
> at
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
> ~[solr-solrj-4.9.0.jar:4.9.0 1604085 - rmuir - 2014-06-20 06:34:04]
> at
> org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:124)
> ~[solr-solrj-4.9.0.jar:4.9.0 1604085 - rmuir - 2014-06-20 06:34:04]
> at org.apache.solr.client.solrj.SolrServer.add(SolrServer.java:116)
> ~[solr-solrj-4.9.0.jar:4.9.0 1604085 - rmuir - 2014-06-20 06:34:04]
> at org.apache.solr.client.solrj.SolrServer.add(SolrServer.java:102)
> ~[solr-solrj-4.9.0.jar:4.9.0 1604085 - rmuir - 2014-06-20 06:34:04]
> {quote}
> I wonder if there is any solution for it?
--
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-6239) HttpSolrServer: connection still allocated
[
https://issues.apache.org/jira/browse/SOLR-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14956356#comment-14956356
]
Mohsen commented on SOLR-6239:
--
Overriding {{createClientConnectionManager()}} and returning
{{PoolingClientConnectionManager}} instead of default
{{BasicClientConnectionManager}} solves this issue.
{code}
@Override
protected ClientConnectionManager createClientConnectionManager() {
return new PoolingClientConnectionManager();
}
{code}
> HttpSolrServer: connection still allocated
> --
>
> Key: SOLR-6239
> URL: https://issues.apache.org/jira/browse/SOLR-6239
> Project: Solr
> Issue Type: Bug
> Components: clients - java
>Reporter: Sergio Fernández
>Priority: Minor
>
> In scenarios where concurrency is aggressive, this exception could easily
> appear:
> {quote}
> org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Invalid
> use of BasicClientConnManager: connection still allocated.
> Make sure to release the connection before allocating another one.
> at
> org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:554)
> ~[solr-solrj-4.9.0.jar:4.9.0 1604085 - rmuir - 2014-06-20 06:34:04]
> at
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
> ~[solr-solrj-4.9.0.jar:4.9.0 1604085 - rmuir - 2014-06-20 06:34:04]
> at
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
> ~[solr-solrj-4.9.0.jar:4.9.0 1604085 - rmuir - 2014-06-20 06:34:04]
> at
> org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:124)
> ~[solr-solrj-4.9.0.jar:4.9.0 1604085 - rmuir - 2014-06-20 06:34:04]
> at org.apache.solr.client.solrj.SolrServer.add(SolrServer.java:116)
> ~[solr-solrj-4.9.0.jar:4.9.0 1604085 - rmuir - 2014-06-20 06:34:04]
> at org.apache.solr.client.solrj.SolrServer.add(SolrServer.java:102)
> ~[solr-solrj-4.9.0.jar:4.9.0 1604085 - rmuir - 2014-06-20 06:34:04]
> {quote}
> I wonder if there is any solution for it?
--
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-4470) Support for basic http auth in internal solr requests
[
https://issues.apache.org/jira/browse/SOLR-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14576198#comment-14576198
]
Fadi Mohsen commented on SOLR-4470:
---
Hi, I saw this issue while trying to package our variant of Solr, the
requirment for production is SSL + Basic Auth.
So I sorrowfully skimmed through this thread, but just before giving up, I
found one can do:
{code}
HttpClientUtil.setConfigurer( new HttpClientConfigurer() {
public void configure(DefaultHttpClient httpClient, SolrParams config) {
// provide own impl of client to be used by Solr for internal
calls.
}
} )
{code}
so running a stand-alone jetty with Solr war, I started setup jetty
programmatically, and then:
{code}
WebAppContext webapp = new WebAppContext();
webapp.setParentLoaderPriority(true);
{code}
setting parent loader prio means treat hole application as a single classpath
kinda.
problem solved for my use case ( green unit tests ), will live test solr cloud,
fingers crossed.
Support for basic http auth in internal solr requests
-
Key: SOLR-4470
URL: https://issues.apache.org/jira/browse/SOLR-4470
Project: Solr
Issue Type: New Feature
Components: clients - java, multicore, replication (java), SolrCloud
Affects Versions: 4.0
Reporter: Per Steffensen
Assignee: Jan Høydahl
Labels: authentication, https, solrclient, solrcloud, ssl
Fix For: Trunk
Attachments: SOLR-4470.patch, SOLR-4470.patch, SOLR-4470.patch,
SOLR-4470.patch, SOLR-4470.patch, SOLR-4470.patch, SOLR-4470.patch,
SOLR-4470.patch, SOLR-4470.patch, SOLR-4470.patch, SOLR-4470.patch,
SOLR-4470.patch, SOLR-4470_branch_4x_r1452629.patch,
SOLR-4470_branch_4x_r1452629.patch, SOLR-4470_branch_4x_r145.patch,
SOLR-4470_trunk_r1568857.patch
We want to protect any HTTP-resource (url). We want to require credentials no
matter what kind of HTTP-request you make to a Solr-node.
It can faily easy be acheived as described on
http://wiki.apache.org/solr/SolrSecurity. This problem is that Solr-nodes
also make internal request to other Solr-nodes, and for it to work
credentials need to be provided here also.
Ideally we would like to forward credentials from a particular request to
all the internal sub-requests it triggers. E.g. for search and update
request.
But there are also internal requests
* that only indirectly/asynchronously triggered from outside requests (e.g.
shard creation/deletion/etc based on calls to the Collection API)
* that do not in any way have relation to an outside super-request (e.g.
replica synching stuff)
We would like to aim at a solution where original credentials are
forwarded when a request directly/synchronously trigger a subrequest, and
fallback to a configured internal credentials for the
asynchronous/non-rooted requests.
In our solution we would aim at only supporting basic http auth, but we would
like to make a framework around it, so that not to much refactoring is
needed if you later want to make support for other kinds of auth (e.g. digest)
We will work at a solution but create this JIRA issue early in order to get
input/comments from the community as early as possible.
--
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-6679) fix or remove suggester from stock solrconfig
[ https://issues.apache.org/jira/browse/SOLR-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14203763#comment-14203763 ] Mohsen commented on SOLR-6679: -- +1 If you add reload() and build() to the subject of this issue more people will vote for this. fix or remove suggester from stock solrconfig - Key: SOLR-6679 URL: https://issues.apache.org/jira/browse/SOLR-6679 Project: Solr Issue Type: Bug Affects Versions: 4.10 Reporter: Yonik Seeley Fix For: 5.0 The stock solrconfig provides a bad experience with a large index... start up Solr and it will spin at 100% CPU for minutes, unresponsive, while it apparently builds a suggester index. -- 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
