[
https://issues.apache.org/jira/browse/SOLR-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley reassigned SOLR-1798:
--
Assignee: Yonik Seeley
> Memory leak in FastLRUCa
I think something would definitely be useful.
Something *short* that people will read and can actually follow.
Something that tells them what we will ask first in trying to diagnose
a problem.
Something/somewhere that they will be likely to run across before
posting a question.
Maybe right near th
[
https://issues.apache.org/jira/browse/SOLR-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839419#action_12839419
]
Yonik Seeley commented on SOLR-1799:
Thanks Chris - this actually is sort of lik
On Sat, Feb 27, 2010 at 9:49 AM, Shalin Shekhar Mangar
wrote:
> But the lucene contrib jars checked in trunk are
> different from the ones on Maven. The revision number is same but the
> date/time of the build is different.
>
> For example, the lucene-analyzers-2.9.2.jar:
> Maven - Implementation-
On Sat, Feb 27, 2010 at 9:34 AM, Mark Miller wrote:
> On 02/27/2010 05:53 AM, Shalin Shekhar Mangar wrote:
>>
>> Any objections?
>>
>
> Didn't rc2 (that we are on) end up being the final release?
Yep - I just updated CHANGES.txt
-Yonik
http://www.lucidimagination.com
[
https://issues.apache.org/jira/browse/SOLR-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839251#action_12839251
]
Yonik Seeley commented on SOLR-1798:
Thanks Laxman, that does look incorrect.
N
[
https://issues.apache.org/jira/browse/SOLR-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838008#action_12838008
]
Yonik Seeley commented on SOLR-1772:
David - I think that could make sense. I'
[
https://issues.apache.org/jira/browse/SOLR-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837480#action_12837480
]
Yonik Seeley commented on SOLR-1791:
I've fixed this in the cloud branch
core names messed up in multicore
-
Key: SOLR-1791
URL: https://issues.apache.org/jira/browse/SOLR-1791
Project: Solr
Issue Type: Bug
Reporter: Yonik Seeley
Priority: Minor
[
https://issues.apache.org/jira/browse/SOLR-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836387#action_12836387
]
Yonik Seeley edited comment on SOLR-1785 at 2/21/10 6:5
[
https://issues.apache.org/jira/browse/SOLR-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836398#action_12836398
]
Yonik Seeley commented on SOLR-1297:
Function queries can contain normal queries, w
[
https://issues.apache.org/jira/browse/SOLR-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836387#action_12836387
]
Yonik Seeley commented on SOLR-1785:
In Solr 1.3 and before, +-Inf were han
Handle +/-Inf, NaN when scoring
Key: SOLR-1785
URL: https://issues.apache.org/jira/browse/SOLR-1785
Project: Solr
Issue Type: Bug
Affects Versions: 1.4
Reporter: Yonik Seeley
[
https://issues.apache.org/jira/browse/SOLR-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836317#action_12836317
]
Yonik Seeley commented on SOLR-1784:
It was an explicit design decision, as show
[
https://issues.apache.org/jira/browse/SOLR-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836309#action_12836309
]
Yonik Seeley commented on SOLR-1784:
Looks like this is working as designed
[
https://issues.apache.org/jira/browse/SOLR-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836173#action_12836173
]
Yonik Seeley commented on SOLR-1772:
Going forward this should be less of an i
[
https://issues.apache.org/jira/browse/SOLR-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1779.
Resolution: Fixed
Fix Version/s: 1.5
this was already committed, closing
[
https://issues.apache.org/jira/browse/SOLR-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836171#action_12836171
]
Yonik Seeley commented on SOLR-1776:
+1, seems reasonable.
> dismax should
[
https://issues.apache.org/jira/browse/SOLR-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835937#action_12835937
]
Yonik Seeley commented on SOLR-1777:
bq. Correction: Tom Hill and I have seen this
[
https://issues.apache.org/jira/browse/SOLR-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley reopened SOLR-1297:
function queries aren't weighted... reopening to track this problem.
> Enable sorting by
[
https://issues.apache.org/jira/browse/SOLR-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835795#action_12835795
]
Yonik Seeley commented on SOLR-1297:
Just curious - what were the reasons behind ad
[
https://issues.apache.org/jira/browse/SOLR-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835451#action_12835451
]
Yonik Seeley commented on SOLR-1777:
bq. Yonik: just to be verify: was this bug
[
https://issues.apache.org/jira/browse/SOLR-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835381#action_12835381
]
Yonik Seeley commented on SOLR-1695:
bq. ...it doesn't require "id"
[
https://issues.apache.org/jira/browse/SOLR-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835347#action_12835347
]
Yonik Seeley commented on SOLR-1568:
I'm not a fan of optional units... I
[
https://issues.apache.org/jira/browse/SOLR-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835343#action_12835343
]
Yonik Seeley commented on SOLR-1695:
bq. the ConvertedLegacyTest failure confuse
[
https://issues.apache.org/jira/browse/SOLR-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835288#action_12835288
]
Yonik Seeley commented on SOLR-1687:
There are a lot of params that people may wan
[
https://issues.apache.org/jira/browse/SOLR-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley reopened SOLR-1695:
reopening - this broke the build.
> Missleading error message when adding docs with missing/multi
[
https://issues.apache.org/jira/browse/SOLR-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835209#action_12835209
]
Yonik Seeley commented on SOLR-1778:
This is a lucene bug: LUCENE-
[
https://issues.apache.org/jira/browse/SOLR-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley reassigned SOLR-1778:
--
Assignee: Yonik Seeley
> java.io.IOException: read past
java.io.IOException: read past EOF
--
Key: SOLR-1778
URL: https://issues.apache.org/jira/browse/SOLR-1778
Project: Solr
Issue Type: Bug
Affects Versions: 1.4
Reporter: Yonik Seeley
[
https://issues.apache.org/jira/browse/SOLR-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1777.
Resolution: Fixed
Fix Version/s: 1.5
committed.
> fields with sortMissingLast don
[
https://issues.apache.org/jira/browse/SOLR-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1777:
---
Attachment: SOLR-1777.patch
OK, here's the final patch with all tests passing.
> fie
[
https://issues.apache.org/jira/browse/SOLR-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835039#action_12835039
]
Yonik Seeley edited comment on SOLR-1777 at 2/18/10 12:2
[
https://issues.apache.org/jira/browse/SOLR-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1777:
---
Attachment: SOLR-1777.patch
The issue had to do with ords and ord normalization in sort-missing-last
fects Versions: 1.4
Reporter: Yonik Seeley
Assignee: Yonik Seeley
Priority: Critical
field types with the sortMissingLast=true attribute can have results sorted
incorrectly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to
[
https://issues.apache.org/jira/browse/SOLR-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832597#action_12832597
]
Yonik Seeley commented on SOLR-1770:
+1
If the normal example is multi-core cap
On Wed, Feb 10, 2010 at 12:02 AM, Jon Gifford wrote:
> Alternatively, I could create a collection per customer, which removes
> the need for slices, but means duplicating the schema many times.
Multiple collections should be able to share a single config (schema
and related config files).
[...]
On Tue, Feb 9, 2010 at 3:10 PM, wrote:
> Author: yonik
> Date: Tue Feb 9 20:10:12 2010
> New Revision: 908194
>
> URL: http://svn.apache.org/viewvc?rev=908194&view=rev
> Log:
> solrj distrib test code - test currently fails when enabled
Scratch that - it was only failing because I had another
[
https://issues.apache.org/jira/browse/SOLR-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831490#action_12831490
]
Yonik Seeley commented on SOLR-1316:
Where are we on this - do people feel it
sponse to shard1."
>>>
>>> This crossed my mind, but my concern was how to handle the case when shard1
>>> never responds. Is this something I need to worry about?
>>>
>>> -mike
>>>
>>> On Sat, Feb 6, 2010 at 11:33 AM, Yonik Seele
It seems like changing an element in a priority queue breaks the
invariants, and hence it's not doable with a priority queue and with
the current strategy of adding sub-responses as they are received.
One way to continue using a priority queue would be to add
sub-responses to the queue in the pref
[
https://issues.apache.org/jira/browse/SOLR-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829812#action_12829812
]
Yonik Seeley commented on SOLR-1754:
bq. Is there really any memory efficiency
On Tue, Feb 2, 2010 at 11:03 PM, Seffie Schwartz wrote:
> I am not having luck doing this. Even though I am specifying -F
> fieldname.separator='|' the fields are
> stored as one field not as multi fields. If I specify -F
> f.fieldname.separator='|' I get a null pointer exception;
How are you
[
https://issues.apache.org/jira/browse/SOLR-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829094#action_12829094
]
Yonik Seeley commented on SOLR-1670:
bq. I guess all along my problem is
[
https://issues.apache.org/jira/browse/SOLR-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829088#action_12829088
]
Yonik Seeley commented on SOLR-1670:
bq. is it possible to only expose the '
[
https://issues.apache.org/jira/browse/SOLR-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829077#action_12829077
]
Yonik Seeley commented on SOLR-1729:
bq. Sounds like DateField would the best candi
[
https://issues.apache.org/jira/browse/SOLR-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806084#action_12806084
]
Yonik Seeley commented on SOLR-1603:
First, some history and motivation from my
[
https://issues.apache.org/jira/browse/SOLR-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805678#action_12805678
]
Yonik Seeley commented on SOLR-1725:
As you pointed out, Java5 is EOL'd alread
[
https://issues.apache.org/jira/browse/SOLR-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805578#action_12805578
]
Yonik Seeley commented on SOLR-1728:
Seems to make sense from a completeness poin
[
https://issues.apache.org/jira/browse/SOLR-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805532#action_12805532
]
Yonik Seeley commented on SOLR-1725:
Cool feature!
Performance:
- It looks
[
https://issues.apache.org/jira/browse/SOLR-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1711.
Resolution: Fixed
Thanks Attila! I just committed this.
> Race condition in
> org/apach
[
https://issues.apache.org/jira/browse/SOLR-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804090#action_12804090
]
Yonik Seeley commented on SOLR-1722:
OK, so normalization to "" instea
Ah thanks - I was going by that comment :-)
On Mon, Jan 18, 2010 at 12:07 PM, Mark Miller wrote:
> Mark Miller wrote:
>> Yonik Seeley wrote:
>>
>>> On Mon, Jan 18, 2010 at 1:17 AM, Chris Hostetter
>>> wrote:
>>>
>>>
>>>> : Right.
On Mon, Jan 18, 2010 at 1:17 AM, Chris Hostetter
wrote:
> : Right... for stock Solr usage (i.e. as long as they don't try to lock
> : the same thing.)
> : It is funny that native locks always work across different processes,
> : but not always in the same JVM though.
>
> Actaully, the more i think
On Thu, Jan 14, 2010 at 2:43 PM, Yonik Seeley
wrote:
> On Thu, Jan 14, 2010 at 1:58 PM, Chris Hostetter
> wrote:
>> : parameter we use for this. Suggestions? logicalshards=shard1,shard2?
>> : lshards=shard1,shard2? slice=shard1,shard2? It doesn't seem like it
>>
[
https://issues.apache.org/jira/browse/SOLR-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801447#action_12801447
]
Yonik Seeley commented on SOLR-1724:
bq. A somewhat secondary issue is whether
On Sun, Jan 17, 2010 at 9:06 AM, Andrzej Bialecki wrote:
> On 2010-01-16 21:11, Yonik Seeley wrote:
>> If we were building from scratch perhaps - but it seems like if we can
>> just model what people do today with Solr (but just make it a lot
>> easier), that's a good s
On Sat, Jan 16, 2010 at 3:40 PM, Chris Hostetter
wrote:
>
> : doc: note about native locks not working for multiple webapps in same JVM
>
> Is this in resposne to the OverlappingFileLockException thread started by
> Joe Kessel? ...
>
> : + native = NativeFSLockFactory - uses OS native file l
On Sat, Jan 16, 2010 at 2:40 PM, Andrzej Bialecki wrote:
> I avoided the word "collection", because Solr deploys various cores under
> "collectionX" names, leading users to assume that core == collection.
For distributed search, it's already common to name the cores the same
thing for shards of t
[
https://issues.apache.org/jira/browse/SOLR-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801255#action_12801255
]
Yonik Seeley commented on SOLR-1724:
{quote}
These are discussed here: http:/
On Fri, Jan 15, 2010 at 7:36 PM, Andrzej Bialecki wrote:
> Hi,
>
> My 0.02 PLN on the subject ...
>
> Terminology
> ---
> First the terminology: reading your emails I have a feeling that my head is
> about to explode. We have to agree on the vocabulary, otherwise we have no
> hope of reach
On Fri, Jan 15, 2010 at 4:12 PM, Jason Rutherglen
wrote:
> The page is huge, which signals to me maybe we're trying to do
> too much
This is really about doing not-so-much in the very near term, while
thinking ahead to the longer term.
> Revamping distributed search could be in a different branc
On Thu, Jan 14, 2010 at 1:38 PM, Ted Dunning wrote:
> I think that most of these complications go away to a remarkable degree if
> you combine katta style random assignment of small shards.
>
> The major simplifications there include:
>
> - no need to move individual documents, nor to split or mer
On Thu, Jan 14, 2010 at 1:38 PM, Yonik Seeley
wrote:
> On Thu, Jan 14, 2010 at 12:46 PM, Yonik Seeley
> wrote:
>> I'm actually starting to lean toward "slice" instead of "logical shard".
Alternate terminology could be "index" for the actual phy
On Thu, Jan 14, 2010 at 1:58 PM, Chris Hostetter
wrote:
> : parameter we use for this. Suggestions? logicalshards=shard1,shard2?
> : lshards=shard1,shard2? slice=shard1,shard2? It doesn't seem like it
> : would be easy to reuse the "shards" parameter for this since it refers
> : to physical sha
[
https://issues.apache.org/jira/browse/SOLR-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800311#action_12800311
]
Yonik Seeley commented on SOLR-1722:
I never really looked at the prev
On Thu, Jan 14, 2010 at 12:46 PM, Yonik Seeley
wrote:
> I'm actually starting to lean toward "slice" instead of "logical shard".
I've gone with this for now and updated http://wiki.apache.org/solr/SolrCloud
but it's certainly not written in stone if peop
On Thu, Jan 14, 2010 at 12:30 PM, Ted Dunning wrote:
> Another concept from Katta that is AFAIK missing from the Solr lexicon is
> the distinction between node and shard. In Katta, a node is a server worker
> instance that contains and queries physical shards.
I think it's sort of missing becaus
partitioning by time or by geo region).
So "slice" would be logical, "shard" would be physical.
To get a full result, one needs to query all of the slices of an
index, but not necessarily all of the shards.
-Yonik
http://www.lucidimagination.com
On Thu, Jan 14, 2010 at 12:
On Thu, Jan 14, 2010 at 12:22 PM, Mark Miller wrote:
> I think we should do both - allow marking any core as the default and
> change our single core example solr.xml to use collection1 rather than
> DEFAULT_CORE.
+1
-Yonik
http://www.lucidimagination.com
The current way of allowing the omission of a core name in the URL is
to name the core DEFAULT_CORE.
While this functionality is great, and allows a multi-core setup to be
back compat with existing URLs, if someone does want to also refer to
the core by it's proper name, it looks pretty ugly. This
The shards parameter currently references physical shards.
There's also a concept of a logical shard (i.e. all physical shards
with identical index content share the same logical shards...
sometimes what I've also called a shard replica).
Should we use logical shard for this, or does anyone have an
[
https://issues.apache.org/jira/browse/SOLR-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799800#action_12799800
]
Yonik Seeley commented on SOLR-1720:
Gah - totally missed that! I saw the syntax J
[
https://issues.apache.org/jira/browse/SOLR-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley closed SOLR-1720.
--
Resolution: Invalid
> replication configuration bug with multiple replicateAfter val
[
https://issues.apache.org/jira/browse/SOLR-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1591:
---
Affects Version/s: (was: 1.4)
1.1.0
Fix Version/s: (was: 1.5
[
https://issues.apache.org/jira/browse/SOLR-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799787#action_12799787
]
Yonik Seeley commented on SOLR-1591:
{quote}
But what about this?
if(map.get(
[
https://issues.apache.org/jira/browse/SOLR-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799779#action_12799779
]
Yonik Seeley commented on SOLR-1591:
bq. Thanks for your last comment, but I
[
https://issues.apache.org/jira/browse/SOLR-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799367#action_12799367
]
Yonik Seeley edited comment on SOLR-1698 at 1/12/10 9:3
[
https://issues.apache.org/jira/browse/SOLR-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799367#action_12799367
]
Yonik Seeley commented on SOLR-1698:
note: it appears that hosts that don't e
Affects Versions: 1.4
Reporter: Yonik Seeley
Fix For: 1.5
Jason reported problems with Multiple replicateAfter values - it worked after
changing to just "commit"
http://www.lucidimagination.com/search/document/e4c9ba46dc03b031/replication_problem
--
This
[
https://issues.apache.org/jira/browse/SOLR-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799283#action_12799283
]
Yonik Seeley commented on SOLR-1698:
committed no-retries on solr_cloud branch.
[
https://issues.apache.org/jira/browse/SOLR-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799250#action_12799250
]
Yonik Seeley commented on SOLR-1698:
This is now part of the solr_cloud branch.
S
On Tue, Jan 12, 2010 at 7:09 AM, Grant Ingersoll wrote:
> I do worry that people will start asking questions about LucidWorks on
> solr-user@, which I'm not sure is appropriate, so we should monitor that
> fairly carefully.
IMO, a single community is better than a split community - so
discussio
[
https://issues.apache.org/jira/browse/SOLR-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1698:
---
Attachment: SOLR-1698.patch
OK, here's a new patch - update trunk first to get the remove
[
https://issues.apache.org/jira/browse/SOLR-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798856#action_12798856
]
Yonik Seeley commented on SOLR-1698:
Hmmm, the rejection had $Id - that might be
[
https://issues.apache.org/jira/browse/SOLR-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1698:
---
Attachment: SOLR-1698.patch
Latest patch, everything back to working. This fixes the load balancing
[
https://issues.apache.org/jira/browse/SOLR-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1707:
---
Attachment: TestPerf.java
Here it is.
To test for size, I cranked up the number of maps to 1M and
[
https://issues.apache.org/jira/browse/SOLR-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798558#action_12798558
]
Yonik Seeley commented on SOLR-1698:
Not sure what's going on... but it seems
[
https://issues.apache.org/jira/browse/SOLR-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798551#action_12798551
]
Yonik Seeley commented on SOLR-1698:
Another problem with the current load balan
[
https://issues.apache.org/jira/browse/SOLR-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1698:
---
Attachment: SOLR-1698.patch
New patch that hooks in load balancing to distributed search.
equivalent
Failure below. Looks like Koji already checked in a fix for it.
Testcase: testPerf took 4.047 sec
Caused an ERROR
undefined field t1
org.apache.solr.common.SolrException: undefined field t1
at org.apache.solr.schema.IndexSchema.getField(IndexSchema.java:1140)
at
org.apach
[
https://issues.apache.org/jira/browse/SOLR-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798252#action_12798252
]
Yonik Seeley commented on SOLR-1657:
bq. But the odd thing about this will be,
[
https://issues.apache.org/jira/browse/SOLR-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798251#action_12798251
]
Yonik Seeley commented on SOLR-1706:
Yep, certainly bugs. IMO, no need to worry a
[
https://issues.apache.org/jira/browse/SOLR-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798243#action_12798243
]
Yonik Seeley commented on SOLR-1709:
Seems useful enough that setting NOW shoul
[
https://issues.apache.org/jira/browse/SOLR-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798234#action_12798234
]
Yonik Seeley commented on SOLR-1710:
bq. For each random string, it compares ou
[
https://issues.apache.org/jira/browse/SOLR-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798203#action_12798203
]
Yonik Seeley commented on SOLR-1709:
Date formatting and parsing also tend t
[
https://issues.apache.org/jira/browse/SOLR-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798188#action_12798188
]
Yonik Seeley commented on SOLR-1657:
What about preserving the attributes for just
[
https://issues.apache.org/jira/browse/SOLR-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798170#action_12798170
]
Yonik Seeley commented on SOLR-1709:
I haven't checked the patch, but it seem
[
https://issues.apache.org/jira/browse/SOLR-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798147#action_12798147
]
Yonik Seeley commented on SOLR-1712:
Also keep in mind that the docset used
[
https://issues.apache.org/jira/browse/SOLR-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1698:
---
Attachment: SOLR-1698.patch
Attaching new patch, still limited to LBHttpSolrServer at this point
101 - 200 of 3185 matches
Mail list logo
