[jira] [Updated] (SOLR-13725) TermsFacetMap.setLimit() unnecessarily rejects negative parameter value

2019-08-28 Thread Richard Walker (Jira)


 [ 
https://issues.apache.org/jira/browse/SOLR-13725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Walker updated SOLR-13725:
--
Priority: Trivial  (was: Major)

> TermsFacetMap.setLimit() unnecessarily rejects negative parameter value
> ---
>
> Key: SOLR-13725
> URL: https://issues.apache.org/jira/browse/SOLR-13725
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: SolrJ
>Affects Versions: 8.2
>Reporter: Richard Walker
>Priority: Trivial
>
> SolrJ's {{TermsFacetMap.setLimit(int maximumBuckets)}} rejects a negative 
> parameter value with an IllegalArgumentException "Parameter 'maximumBuckets' 
> must be non-negative".
> But a negative value for the limit parameter is accepted by Solr server, and 
> is meaningful: i.e., it means "no limit".
> The {{setLimit()}} method shouldn't reject a negative parameter value.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Created] (SOLR-13725) TermsFacetMap.setLimit() unnecessarily rejects negative parameter value

2019-08-28 Thread Richard Walker (Jira)
Richard Walker created SOLR-13725:
-

 Summary: TermsFacetMap.setLimit() unnecessarily rejects negative 
parameter value
 Key: SOLR-13725
 URL: https://issues.apache.org/jira/browse/SOLR-13725
 Project: Solr
  Issue Type: Bug
  Security Level: Public (Default Security Level. Issues are Public)
  Components: SolrJ
Affects Versions: 8.2
Reporter: Richard Walker


SolrJ's {{TermsFacetMap.setLimit(int maximumBuckets)}} rejects a negative 
parameter value with an IllegalArgumentException "Parameter 'maximumBuckets' 
must be non-negative".

But a negative value for the limit parameter is accepted by Solr server, and is 
meaningful: i.e., it means "no limit".

The {{setLimit()}} method shouldn't reject a negative parameter value.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-12858) EmbeddedSolrServer POST method has contentType issue

2019-07-23 Thread Richard Walker (JIRA)


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

Richard Walker commented on SOLR-12858:
---

Just ran into this on 8.1.1.

I use an HttpSolrClient with a standalone Solr for production use, but an 
EmbeddedSolrServer for my test suite.

I just switched from GET to POST precisely to cope with large query strings, 
and now my test suite fails. Workaround for now in this case is to change my 
search method to do an instanceof test on the client before running the query, 
which (of course) is  the sort of thing I want to avoid.

 

> EmbeddedSolrServer POST method has contentType issue
> 
>
> Key: SOLR-12858
> URL: https://issues.apache.org/jira/browse/SOLR-12858
> Project: Solr
>  Issue Type: Bug
>Affects Versions: 7.4, 7.5
>Reporter: Phillip Klinefelter
>Priority: Major
>
> EmbeddedSolrServer will fail with the following exception when using a POST 
> method.
> {{org.apache.solr.common.SolrException: Bad contentType for search handler 
> :application/javabin request=\{q=*:*}}}{{    at 
> org.apache.solr.request.json.RequestUtil.processParams(RequestUtil.java:73)}}
> {{     at 
> org.apache.solr.util.SolrPluginUtils.setDefaults(SolrPluginUtils.java:167)}}
> {{     at 
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:196)}}
> {{     at org.apache.solr.core.SolrCore.execute(SolrCore.java:2539)}}
> {{     at 
> org.apache.solr.client.solrj.embedded.EmbeddedSolrServer.request(EmbeddedSolrServer.java:191)}}
> {{     at 
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:194)}}
> {{     at org.apache.solr.client.solrj.SolrClient.query(SolrClient.java:974)}}
> {{     at org.apache.solr.client.solrj.SolrClient.query(SolrClient.java:990)}}
> A POST method can be added to TestEmbeddedSolrServerConstructors to reproduce 
> or do the following.
> {{embeddedSolrServer.query(new SolrQuery("*:*"), SolrRequest.METHOD.POST);}}
> This worked before Solr 7.4.  The issue appears to have been caused by 
> changes made in SOLR-12142 based on debugging and a discussion I had with 
> [~dsmiley].
> CC [~noble.paul]
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Created] (SOLR-13646) Documentation about plugin JARs in SolrCloud mode either incomplete or doesn't match available functionality

2019-07-22 Thread Richard Walker (JIRA)
Richard Walker created SOLR-13646:
-

 Summary: Documentation about plugin JARs in SolrCloud mode either 
incomplete or doesn't match available functionality
 Key: SOLR-13646
 URL: https://issues.apache.org/jira/browse/SOLR-13646
 Project: Solr
  Issue Type: Bug
  Security Level: Public (Default Security Level. Issues are Public)
  Components: documentation, Plugin system, SolrCloud
Affects Versions: 8.1.1
Reporter: Richard Walker


(As originally "discussed" on mailing list at 
[http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201907.mbox/%3cae3e5dbe-0d38-4594-b82a-ceab4e024...@ardc.edu.au%3e])

I'm trying to use a plugin JAR containing a custom query parser.

I've been able to get this to work the "simple" way, by putting the JAR in the 
file system, and specifying basic
{code:java}
  
  
{code}
values in {{solrconfig.xml}}. No problem doing it this way.

But I'm running in SolrCloud mode and I'd like to take advantage of an option 
that the user guide seems to offer at this page:

[https://lucene.apache.org/solr/guide/8_1/resource-and-plugin-loading.html]

But, so far, I don't see how to make it work.

To be specific, I'm trying to use this idea:
{quote}Resources and plugins may be stored:
 * in ZooKeeper under a collection’s configset node (SolrCloud only);{quote}
Note: I'm _not_ trying to do the _third_ option listed, i.e.:
{quote} * in Solr’s Blob Store (SolrCloud only)", that uses the ".system" 
collection.{quote}
The user guide seems to suggest that I can upload the JAR to the collection's 
config using {{zk cp}}:

"To upload a plugin or resource to a configset already stored on ZooKeeper, you 
can use {{bin/solr zk cp}}."

So, I've used zk cp to upload the JAR to 
{{zk:/configs/my_collection/my_plugin.jar}}

(I also tried various other subdirectories such as 
{{zk:/configs/my_collection/lib/my_plugin.jar}})

So far, so good. But now how do I refer to the JAR in {{solrconfig.xml}}? The 
user guide doesn't really say.

I've tried specifying the location of the JAR with various values of {{}} element.

No success at all; I only get a {{ClassNotFoundException}} for the plugin class.

So, it seems that the documentation is _at least_ missing information about how 
to specify the location of a plugin JAR stored "in ZooKeeper under a 
collection’s configset node".

I found this earlier thread: 
[http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201701.mbox/%3ccakhkodqv-y59+7m86ogvf1feqj6ieiogp8trhl1mg5fuajl...@mail.gmail.com%3e]

in which the second message (from Shawn Heisey) says:
{quote}I actually do not know what the path for lib directives is relative to 
when running SolrCloud. Most things in a core config are relative to the 
location of the config file itself, but in this case, the config file is not on 
the filesystem at all, it's in zookeeper, and I don't think Solr can use jars 
in zookeeper.
{quote}
So, if this is right, it seems that the documentation is in this case offering 
functionality that does not exist. (And, once again, I am _not_ talking about 
"Solr’s Blob Store ... that uses the .system collection", which I don't want to 
use.)

Richard.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org