We use Toke's scenario in a couple places too. We are capable writing a URP
that does it, but it feels dirty, and replacing config with code seems like
something it makes sense to avoid.
Having top level support of some kind of analysis in URP or somewhere else
can also help in other situations wh
I haven't tried for 95th percentile, but generally with those collection
start stats you would monitor based on calculated deltas. You can figure
out the average response time for any given window of time not smaller than
your snapshot polling interval. I don't see why 95th percentile would be
an
[
https://issues.apache.org/jira/browse/SOLR-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542888#comment-15542888
]
Ryan Josal commented on SOLR-4736:
--
I just came across a use case where this woul
[
https://issues.apache.org/jira/browse/LUCENE-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396928#comment-15396928
]
Ryan Josal commented on LUCENE-2899:
Seconded, this is really useful stuff.
&
>
>
>
> -
>
> Uwe Schindler
>
> H.-H.-Meier-Allee 63, D-28213 Bremen
>
> http://www.thetaphi.de
>
> eMail: u...@thetaphi.de
>
>
>
> *From:* rjo...@gmail.com
> [mailto:
> rjo...@gmail.com ] *On
> Behalf Of *Ryan Josal
> *Sent:* Monday, May 16,
+1 it's a pain for plugin development too. Extending JSONResponseWriter
comes to mind.
On Monday, May 16, 2016, Chris Hostetter wrote:
>
> : I found out that there are more of those in the facets module. Can we
> : change those to be real *inner* classes or put them in separate files?
>
> +1 ..
I don't have a comment on whether or not it makes sense to have schedule
based merges, but I will say that search speed is impacted by segment
count, and if you're indexing constantly all day long, it's possible that
saving a merge until off peak hours may put more stress on your servers
than doing
butors group. You should be able to comment
>>> on JIRAs now.
>>>
>>> On Thu, Apr 21, 2016 at 8:51 PM, Ryan Josal >> > wrote:
>>>
>>>> Woah, yeah, I have filed a few bugs as well as posted patches and
>>>> comments. Indeed I don&
Woah, yeah, I have filed a few bugs as well as posted patches and
comments. Indeed I don't seem to be able to comment anymore. Anyone want
to add me (rjosal) to a role that can comment or create?
Ryan
On Thursday, April 21, 2016, David Smiley wrote:
> Wow! My reading of this is that the gene
My understanding is a Term is comprised of a "token" and a field. So then
the documentation makes sense to me - return the count of tokens in a field
for example. But there were a couple of references you had there that
don't match with that definition, like the number of tokens in a
collection.
[
https://issues.apache.org/jira/browse/SOLR-8812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201525#comment-15201525
]
Ryan Josal commented on SOLR-8812:
--
On the topic of SOLR-2649, I just upgraded to
.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Thu, Feb 25, 2016 at 6:10 PM, Ryan Josal > wrote:
> > I know, there's a ton of documentation about the query parser whitespace
> > issue, and there's also a fair bit of info on the pos
I know, there's a ton of documentation about the query parser whitespace
issue, and there's also a fair bit of info on the positionLengthAttribute
issue, but I seem to have stumbled upon a new issue with multi term
synonyms: it doesn't seem to play well with a bunch of tokens in the same
position.
I ran into an issue that seems to be undesirable behavior to me, but
considering how long query elevation has been around, maybe there are use
cases for it as is.
I set the QE analyzer to WhitespaceTokenizer -> LowercaseFilter.
When QE loads the xml file and it analyzes the queries into keys, it
should probably be a bug?
>>
>> -Yonik
>>
>>
>> On Tue, Dec 15, 2015 at 7:55 PM, Jack Krupansky
>> > > wrote:
>> > Yonik? The doc is weak in this area. In fact, I see a comment on it from
>> > Cassandra directed to you to verify the JSON to p
I didn't see a Jira open in this, so I wanted to see if it's expected. If
you pass "fields":[...] in a SOLR JSON API request, it does not override
what's the default in the handler config. I had fl=* as a default, so I
saw "fields" have no effect, while "params":{"fl":...} worked as expected.
Afte
[
https://issues.apache.org/jira/browse/SOLR-8175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032697#comment-15032697
]
Ryan Josal commented on SOLR-8175:
--
Thanks for picking it up!
> Wordbreak spell
ch, attached to the jira of course. But it
> should work with SolrCloud too.
>
> On Mon, Nov 23, 2015 at 9:05 PM, Ryan Josal > wrote:
>
>> +1 for making new facet sorts easier to implement. I implemented an
>> order where the come back in order they are first seen in the
+1 for making new facet sorts easier to implement. I implemented an order
where the come back in order they are first seen in the doclist, but it
didn't come out very clean. My approach was to extend FacetComponent, and
resort the facets by pulling them out of the results and putting them back
(a
[
https://issues.apache.org/jira/browse/SOLR-8175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974575#comment-14974575
]
Ryan Josal commented on SOLR-8175:
--
BTW, this patch passes "ant test" and
[
https://issues.apache.org/jira/browse/SOLR-8175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Josal updated SOLR-8175:
-
Attachment: solr8175.patch
Uploaded solr8175.patch, which includes an updated unit test which would throw
Ryan Josal created SOLR-8175:
Summary: Wordbreak spellchecker throws IOOBE with Occur.MUST term
Key: SOLR-8175
URL: https://issues.apache.org/jira/browse/SOLR-8175
Project: Solr
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-6842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14963326#comment-14963326
]
Ryan Josal commented on LUCENE-6842:
FWIW, I have seen an OOME due to a large nu
fore you sent to dev.
>
> General info: The canonical and official repository for Lucene/Solr is
> in SVN. There are two public git mirrors. One at git.apache.org, one
> is at github.
>
> On 10/16/2015 11:07 AM, Ryan Josal wrote:
> > *) how do I properly fork it o
Hi guys, new subscriber here, so as a bit of an intro, I'm a long time user
of Lucene/Solr from Lucene 1.x. I've plugged everything pluggable and am
quite familiar with the core Lucene and solr code. Looks like I should
have sent this to dev instead of solr-user:
I'd like to get your tips on how
Ryan Josal created SOLR-7953:
Summary: BaseEditorialTransformer (elevated) doesn't work with
LazyField
Key: SOLR-7953
URL: https://issues.apache.org/jira/browse/SOLR-7953
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622449#comment-14622449
]
Ryan Josal edited comment on SOLR-6234 at 7/10/15 3:22 PM:
---
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622449#comment-14622449
]
Ryan Josal commented on SOLR-6234:
--
It seems like the parser can find out if
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621658#comment-14621658
]
Ryan Josal commented on SOLR-6234:
--
That makes a lot of sense David, I would prefer
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619521#comment-14619521
]
Ryan Josal edited comment on SOLR-6234 at 7/8/15 10:47 PM:
---
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Josal updated SOLR-6234:
-
Attachment: otherHandler.patch
I've attached otherHandler.patch, which is a patch on top of the exi
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619385#comment-14619385
]
Ryan Josal commented on SOLR-6234:
--
That will be great Tim! For my personal use cas
Ryan Josal created SOLR-7726:
Summary: CodecFactory plugins are double informed of SolrCore
Key: SOLR-7726
URL: https://issues.apache.org/jira/browse/SOLR-7726
Project: Solr
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586457#comment-14586457
]
Ryan Josal commented on SOLR-6234:
--
[~neerajlajpal], glad you got it working. T
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586444#comment-14586444
]
Ryan Josal commented on SOLR-6234:
--
I've been using this for a few days now, and
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583437#comment-14583437
]
Ryan Josal edited comment on SOLR-6234 at 6/12/15 2:1
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583437#comment-14583437
]
Ryan Josal edited comment on SOLR-6234 at 6/12/15 2:1
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583437#comment-14583437
]
Ryan Josal commented on SOLR-6234:
--
[~neerajlajpal] Solr parses the value of q wi
[
https://issues.apache.org/jira/browse/SOLR-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579608#comment-14579608
]
Ryan Josal commented on SOLR-6234:
--
This is awesome, the normal !join qparser is ma
Ryan Josal created SOLR-7152:
Summary: Cannot override default rq with no rankquery
Key: SOLR-7152
URL: https://issues.apache.org/jira/browse/SOLR-7152
Project: Solr
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/SOLR-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146798#comment-14146798
]
Ryan Josal commented on SOLR-3015:
--
I ran into a problem with this today. I ha
[
https://issues.apache.org/jira/browse/SOLR-6396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105662#comment-14105662
]
Ryan Josal commented on SOLR-6396:
--
Confirmed it does work the way Hoss suggests; u
[
https://issues.apache.org/jira/browse/SOLR-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534434#comment-13534434
]
Ryan Josal commented on SOLR-3083:
--
I applied this patch to Solr 3.6 - I notice
[
https://issues.apache.org/jira/browse/SOLR-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496352#comment-13496352
]
Ryan Josal commented on SOLR-3866:
--
The use case I (and it appears the author of
44 matches
Mail list logo
