StreamingUpdateSolrServer hangs
---
Key: SOLR-1885
URL: https://issues.apache.org/jira/browse/SOLR-1885
Project: Solr
Issue Type: Bug
Reporter: Yonik Seeley
Fix For: 3.1
Looks like we
[
https://issues.apache.org/jira/browse/SOLR-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1703:
---
Fix Version/s: 3.1
Sorting by function problems on multicore (more than one core
On Wed, Apr 14, 2010 at 2:43 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
1) does anyone understand why this is failing?
The compiler barfed... (a compiler bug.)
I updated it to use the Java6 compiler this morning.
I had previously disabled the nightly test and build part, but kept
the
Yes, it requires that Solr in general is compiled with Java6. We
should make our lives easier and make Java6 a Solr requirement.
Zookeeper requires Java6, and we also want Java6 for some of the
scripting capabilities.
-Yonik
Apache Lucene Eurocon 2010
18-21 May 2010 | Prague
On Wed, Apr 14,
[
https://issues.apache.org/jira/browse/SOLR-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12856517#action_12856517
]
Yonik Seeley commented on SOLR-1632:
Rewrite not working through function query
[
https://issues.apache.org/jira/browse/SOLR-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12856212#action_12856212
]
Yonik Seeley commented on SOLR-1873:
bq. As I wrap up the remaining work here, one issue
[
https://issues.apache.org/jira/browse/SOLR-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12856220#action_12856220
]
Yonik Seeley commented on SOLR-1632:
Was looking into this a little offline with Mark
: Yonik Seeley
Assignee: Yonik Seeley
A little stepping stone to NRT:
Per-segment single-valued string faceting using the Lucene FieldCache.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https
[
https://issues.apache.org/jira/browse/SOLR-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12855576#action_12855576
]
Yonik Seeley commented on SOLR-1875:
OK, so the idea is pretty simple: reuse
[
https://issues.apache.org/jira/browse/SOLR-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1875:
---
Attachment: SOLR-1875.patch
Here's the first cut - seems to work fine.
You can try it out
[
https://issues.apache.org/jira/browse/SOLR-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12855661#action_12855661
]
Yonik Seeley commented on SOLR-1873:
I just checked in a fix to the terms component
On Thu, Apr 8, 2010 at 1:37 PM, Mark Miller markrmil...@gmail.com wrote:
I'd like to merge solr cloud into trunk -
Sounds like a good idea to me.
-Yonik
http://www.lucidimagination.com
I think there may be some more polish to do, but its pretty close, and back
compatible if you choose not
[
https://issues.apache.org/jira/browse/SOLR-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12855125#action_12855125
]
Yonik Seeley commented on SOLR-1871:
Yep, makes sense. Some of the older
Hmmm, interesting. A few hours ago I deleted them all because they
were stale, and put a readme that pointed to the hudson built
downloads... but that readme doesn't look like it's being picked up.
http://hudson.zones.apache.org/hudson/job/Solr-trunk/lastSuccessfulBuild/artifact/trunk/solr/dist/
On Wed, Apr 7, 2010 at 11:38 AM, Yonik Seeley
yo...@lucidimagination.com wrote:
Hmmm, interesting. A few hours ago I deleted them all because they
were stale, and put a readme that pointed to the hudson built
downloads... but that readme doesn't look like it's being picked up.
OK, I changed
[
https://issues.apache.org/jira/browse/SOLR-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853377#action_12853377
]
Yonik Seeley commented on SOLR-1568:
bq. I wonder if we shouldn't also pass along
[
https://issues.apache.org/jira/browse/SOLR-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853401#action_12853401
]
Yonik Seeley commented on SOLR-1568:
bq. even better. Patch soon
I meant, you already
[
https://issues.apache.org/jira/browse/SOLR-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853135#action_12853135
]
Yonik Seeley commented on SOLR-1860:
How many languages are we talking?
I like
[
https://issues.apache.org/jira/browse/SOLR-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12852094#action_12852094
]
Yonik Seeley commented on SOLR-1857:
I just did a 5 min review, not line-by-line
On Tue, Mar 30, 2010 at 8:06 AM, Robert Muir rcm...@gmail.com wrote:
We have two choices:
* we could treat this stuff as impl details, and add protwords.txt support
to all stemming factories. we could just wrap the filter with a
keywordmarkerfilter internally.
* we could deprecate the
On Tue, Mar 30, 2010 at 10:07 AM, Robert Muir rcm...@gmail.com wrote:
Sorta unrelated too, but on the same topic of performance, I'd really like
to improve the indexing speed with the example schema, and thats my hidden
motivation here.
I think we've already significantly improved WDF and
I've opened an issue for this:
https://issues.apache.org/jira/browse/INFRA-2580
-Yonik
http://www.lucidimagination.com
On Tue, Mar 30, 2010 at 11:27 AM, David Smiley (@MITRE.org)
dsmi...@mitre.org wrote:
It absolutely is a better way to collaborate on development, especially in
conjunction
[
https://issues.apache.org/jira/browse/SOLR-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12851098#action_12851098
]
Yonik Seeley commented on SOLR-1848:
bq. Frankly though: the queries.html is so simple
[
https://issues.apache.org/jira/browse/SOLR-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12851154#action_12851154
]
Yonik Seeley commented on SOLR-1568:
Things are looking good! I like
[
https://issues.apache.org/jira/browse/SOLR-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850251#action_12850251
]
Yonik Seeley commented on SOLR-1848:
What's the motivation for including them
[
https://issues.apache.org/jira/browse/SOLR-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850256#action_12850256
]
Yonik Seeley commented on SOLR-1848:
I believe the tutorial is already shipped
[
https://issues.apache.org/jira/browse/SOLR-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850257#action_12850257
]
Yonik Seeley commented on SOLR-1848:
This also complicates setting up with different
[
https://issues.apache.org/jira/browse/SOLR-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850267#action_12850267
]
Yonik Seeley commented on SOLR-1835:
As a further attempt to clean up example and make
[
https://issues.apache.org/jira/browse/SOLR-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850269#action_12850269
]
Yonik Seeley commented on SOLR-1848:
If it's not worth the discussion, hopefully you
[
https://issues.apache.org/jira/browse/SOLR-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850274#action_12850274
]
Yonik Seeley commented on SOLR-1848:
I guess an argument could also be made for putting
[
https://issues.apache.org/jira/browse/SOLR-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850276#action_12850276
]
Yonik Seeley commented on SOLR-1848:
bq. Just b/c you don't find something useful
[
https://issues.apache.org/jira/browse/SOLR-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850289#action_12850289
]
Yonik Seeley commented on SOLR-1835:
Mark pointed out that removing multicore is related
[
https://issues.apache.org/jira/browse/SOLR-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850329#action_12850329
]
Yonik Seeley commented on SOLR-1848:
OK, I've reverted this for now.
If people want
[
https://issues.apache.org/jira/browse/SOLR-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850367#action_12850367
]
Yonik Seeley commented on SOLR-1850:
Thanks for catching this John, copying the whole
[
https://issues.apache.org/jira/browse/SOLR-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850392#action_12850392
]
Yonik Seeley commented on SOLR-1850:
Yes, that's definitely the way to go
[
https://issues.apache.org/jira/browse/SOLR-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1850.
Resolution: Fixed
Fix Version/s: 3.1
Thanks John, I've committed this suggestion along
Reporter: Yonik Seeley
Fix For: 3.1
The terms component uses a named list instead of simple ordered map for it's
top-level data structure.
Access by name is more important, so it should be a map.
--
This message is automatically generated by JIRA.
-
You can reply
[
https://issues.apache.org/jira/browse/SOLR-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849685#action_12849685
]
Yonik Seeley commented on SOLR-1845:
Remember to check the JSON output for new request
[
https://issues.apache.org/jira/browse/SOLR-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849754#action_12849754
]
Yonik Seeley commented on SOLR-1845:
bq. Isn't getting the terms in order more important
[
https://issues.apache.org/jira/browse/SOLR-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1845:
---
Attachment: SOLR-1845.patch
Attaching patch.
This is mostly a back compat issue for JSON based output
[
https://issues.apache.org/jira/browse/SOLR-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1845.
Resolution: Fixed
Committed.
terms component response format uses list instead of map
[
https://issues.apache.org/jira/browse/SOLR-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1835:
---
Attachment: SOLR-1835_example_junit4.patch
Attaching patch with the beginnings of migrating some
For Solr, we can just move the current trunk to a 15 branch.
-Yonik
On Tue, Mar 23, 2010 at 9:39 AM, Grant Ingersoll gsing...@apache.org wrote:
On Mar 22, 2010, at 8:27 AM, Uwe Schindler wrote:
Hi all,
the discussion where to do the development after the merge, now gets actual:
Currently
[
https://issues.apache.org/jira/browse/SOLR-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1835:
---
Attachment: SOLR-1835-ignoreExceptions.patch
Here's a patch that tries to allow us to avoid spitting
On Tue, Mar 23, 2010 at 10:49 AM, Grant Ingersoll gsing...@apache.org wrote:
On Mar 23, 2010, at 10:09 AM, Grant Ingersoll wrote:
3. Other nightly build stuff. My cron tabs, etc. I will update them to
point at the new trunk.
OK, I updated my cron tab for the site check out of Lucene.
[
https://issues.apache.org/jira/browse/SOLR-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848761#action_12848761
]
Yonik Seeley commented on SOLR-1835:
scratch that - it did work from the command line
[
https://issues.apache.org/jira/browse/SOLR-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1835:
---
Attachment: SOLR-1835-ignoreExceptions.patch
Upated exception ignore patch and some converted tests
[
https://issues.apache.org/jira/browse/SOLR-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848792#action_12848792
]
Yonik Seeley commented on SOLR-1835:
OK, I've committed the exception logging ignore
On Mon, Mar 22, 2010 at 2:20 PM, Ryan McKinley ryan...@gmail.com wrote:
I'm confused... what is the need for a new name? The only place where
there is a conflict is in the top level svn tree...
Agree, no need to re-brand.
What about something general like:
[
https://issues.apache.org/jira/browse/SOLR-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1797:
---
Attachment: SOLR-1797.patch
Patch attached:
- makes lists synchronized for thread safety
- adds
[
https://issues.apache.org/jira/browse/SOLR-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1797.
Resolution: Fixed
Fix Version/s: 1.5
Committed to newtrunk, and merged back to trunk.
I
website merge related changes
-
Key: SOLR-1836
URL: https://issues.apache.org/jira/browse/SOLR-1836
Project: Solr
Issue Type: Improvement
Reporter: Yonik Seeley
Priority: Minor
Website
[
https://issues.apache.org/jira/browse/SOLR-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847780#action_12847780
]
Yonik Seeley commented on SOLR-1836:
At a minimum, we should have a shared committer
[
https://issues.apache.org/jira/browse/SOLR-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1836:
---
Attachment: SOLR-1836_lucene.patch
SOLR-1836_solr.patch
Here's a simple patch
speed up and improve tests
--
Key: SOLR-1835
URL: https://issues.apache.org/jira/browse/SOLR-1835
Project: Solr
Issue Type: Improvement
Reporter: Yonik Seeley
Fix For: 3.1
General test
[
https://issues.apache.org/jira/browse/SOLR-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1835:
---
Attachment: SOLR-1835.patch
Attaching a first cut at a SolrTestCaseJ4 that extends LuceneTestCaseJ4
[
https://issues.apache.org/jira/browse/SOLR-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847557#action_12847557
]
Yonik Seeley commented on SOLR-1830:
So... I went and coded up a quick class to switch
On Fri, Mar 19, 2010 at 7:31 PM, KaktuChakarabati jimmoe...@gmail.com wrote:
In particular, it looks like this can be traced to a non-thread safe
iteration over infoMBeans (ArrayList) in SolrResourceLoader::inform()
I looked for some recent changes to that area of code and traced it to
[
https://issues.apache.org/jira/browse/SOLR-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846891#action_12846891
]
Yonik Seeley commented on SOLR-1830:
The issue was that the writer being opened
[
https://issues.apache.org/jira/browse/SOLR-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1379.
Resolution: Fixed
Fix Version/s: (was: 1.5)
3.1
Add
[
https://issues.apache.org/jira/browse/SOLR-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846896#action_12846896
]
Yonik Seeley commented on SOLR-1830:
A quick datapoint - BasicFunctionalityTest dropped
On Thu, Mar 18, 2010 at 10:11 AM, Ryan McKinley ryan...@gmail.com wrote:
Is there any reason why CoreContainer shouldn't throw an exception if
solr.xml declares a core w/o a name, or two cores with the same name?
This makes sense. I think WAY WAY back (in a patch), cores could be
On Thu, Mar 18, 2010 at 1:12 PM, Michael McCandless
luc...@mikemccandless.com wrote:
Ahh, OK.
Meaning Solr will have to remove deprecated support, which means
Solr's next released version would be a major release? Ie 2.0?
I've been working on the assumption of 3.1 - matching Lucene.
Solr
On Thu, Mar 18, 2010 at 2:01 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
I thinks solr-3.1 only makes sense if Solr is include in one big
giant apache-lucene-3.1.tgz release
Projects have multiple artifacts all the time for user convenience.
Binary vs source downloads, different subsets
On Thu, Mar 18, 2010 at 2:16 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
3.1 may make life easy for us as developers, but is likely to be just as
cofusing to users as if we called the next version Q
We're jumping to version 3.1 because we're releasing at the same time,
and are based on
On Thu, Mar 18, 2010 at 2:36 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
: We're jumping to version 3.1 because we're releasing at the same time,
: and are based on Lucene 3.1.
You say it like it's a done deal, but I don't get the impression
that i'm the only one who thinks it's
On Thu, Mar 18, 2010 at 2:49 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
Use 3.1 and developers in the know will understand that i's because we're
using LuceneJava 3.1; but uninformed users *might* be confused as to why
it jumped to a (seemingly) arbitrary number.
I also like to look
[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847175#action_12847175
]
Yonik Seeley commented on SOLR-1817:
bq. I'm starting to think the whole idea
On Wed, Mar 17, 2010 at 8:15 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
: No, actaully it's the converse issue -- if a major piece moves from solr
: to core and a *person* wanted to make a major change to that piece of
: functionality that wasn't backwards compatible, then core
On Wed, Mar 17, 2010 at 9:16 PM, Grant Ingersoll gsing...@apache.org wrote:
I tend to agree w/ Hoss here. I don't think we have to be the same version
numbers and I don't think we absolutely have to do lockstep releases.
No one said absolutely.
It's important to try and release at the same
[
https://issues.apache.org/jira/browse/SOLR-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846725#action_12846725
]
Yonik Seeley commented on SOLR-1553:
Hmmm, the intention was to try and detect when
[
https://issues.apache.org/jira/browse/SOLR-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846730#action_12846730
]
Yonik Seeley commented on SOLR-1379:
Haha - I just write almost the exact same
[
https://issues.apache.org/jira/browse/SOLR-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846732#action_12846732
]
Yonik Seeley commented on SOLR-1379:
Thanks Alex! I've committed this on branches
tests should be able to use RAMDirectory
Key: SOLR-1830
URL: https://issues.apache.org/jira/browse/SOLR-1830
Project: Solr
Issue Type: Improvement
Reporter: Yonik Seeley
[
https://issues.apache.org/jira/browse/SOLR-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846747#action_12846747
]
Yonik Seeley commented on SOLR-1830:
Adding directoryFactory name=DirectoryFactory
Here is a very rough list of what makes sense to me:
- since lucene is on a new major version, the next solr release
containing that sould have a new major version number
- this does not preclude further releases on 1.x
- for simplicity, and the single dev model, we should just sync
with
the lucene sources (i.e it
works in the IDE, but not on the command line right now).
-Yonik
On Tue, Mar 16, 2010 at 10:00 AM, Yonik Seeley yo...@apache.org wrote:
Here is a very rough list of what makes sense to me:
- since lucene is on a new major version, the next solr release
containing
On Tue, Mar 16, 2010 at 10:45 AM, Grant Ingersoll gsing...@apache.org wrote:
On Mar 16, 2010, at 11:00 AM, Yonik Seeley wrote:
Here is a very rough list of what makes sense to me:
- since lucene is on a new major version, the next solr release
containing that sould have a new major version
be
the key there we don't have that currently.
-Yonik
On Tue, Mar 16, 2010 at 10:06 AM, Yonik Seeley yo...@apache.org wrote:
another minor addition:
- move to Junti4 for new tests... and some old tests might be
migrated (for speed issues)
I already have a SolrTestCaseJ4 that extends
On Tue, Mar 16, 2010 at 1:47 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
even if we get Lucene-Java and Solr onto the same
scheme now, we could easily find ourselves in a situation where
we're ready to release lucene-3.3 (ie: a minor release that is
back-compat with lucene-3.2 and
On Tue, Mar 16, 2010 at 2:25 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
: We try not to do that then. Things make a lot more sense when one
: starts thinking of them as a single project, w/o multiple downloads.
:
: If major modules were to be pulled from Solr and put into Lucene,
partial field types created on error
Key: SOLR-1824
URL: https://issues.apache.org/jira/browse/SOLR-1824
Project: Solr
Issue Type: Bug
Affects Versions: 1.1.0
Reporter: Yonik Seeley
[
https://issues.apache.org/jira/browse/SOLR-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845319#action_12845319
]
Yonik Seeley commented on SOLR-1824:
The partial field is created regardless
Due to a tremendous amount of work by our newly merged committer
corps, the get-on-lucene-trunk branch (branches/solr) is ready for
prime-time as the new solr trunk! Lucene and Solr need to move to a
common trunk for a host of reasons, including single patches that can
cover both, shared tags and
[
https://issues.apache.org/jira/browse/SOLR-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845121#action_12845121
]
Yonik Seeley commented on SOLR-1820:
sounds fine - we should be bumping major version
The lucene/solr merge* has started off with a bang!
Development on branches/solr to get on lucene trunk is progressing at
a furious (nay... ferocious) pace, pushed by the not new, but new to
solr committers. Feels great to have everyone on the same team!
We've already merged committers of course
[
https://issues.apache.org/jira/browse/SOLR-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1815.
Resolution: Fixed
Fix Version/s: 1.5
Committed. I almost didn't add a CHANGES entry
[
https://issues.apache.org/jira/browse/SOLR-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844668#action_12844668
]
Yonik Seeley commented on SOLR-1815:
I'll go ahead and make this change soon
On Fri, Mar 12, 2010 at 3:37 PM, Frank Wesemann
f.wesem...@fotofinder.net wrote:
Hello,
I don't want to roll up all the XMLWriter issues, but stumpled upon this:
http://lucene.apache.org/solr/api/org/apache/solr/response/SolrQueryResponse.html#returnable_data
says that a Map containing any of
Interesting looking stuff Marcus!
Seems sort of related to stat.facet (calc stats on unique facet values)
http://wiki.apache.org/solr/StatsComponent
On Thu, Mar 11, 2010 at 5:49 PM, Marcus Herou
marcus.he...@tailsweep.com wrote:
I have now implemented Facet with FunctionQueries it is really
[
https://issues.apache.org/jira/browse/SOLR-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843363#action_12843363
]
Yonik Seeley commented on SOLR-1808:
bq. Solr is maintaining a heavy weight Searcher
[
https://issues.apache.org/jira/browse/SOLR-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842480#action_12842480
]
Yonik Seeley commented on SOLR-1297:
Finally got a chance to check this out a little
[
https://issues.apache.org/jira/browse/SOLR-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842493#action_12842493
]
Yonik Seeley commented on SOLR-1297:
bq. Not sure I understand this, I didn't write any
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
[
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 FastLRUCache
[
https://issues.apache.org/jira/browse/SOLR-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1798:
---
Attachment: SOLR-1798.patch
I think the fix is as simple as this patch.
Verifying that it fixes
[
https://issues.apache.org/jira/browse/SOLR-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842319#action_12842319
]
Yonik Seeley commented on SOLR-1798:
Hmmm, right - fixes the memory leak, but breaks
[
https://issues.apache.org/jira/browse/SOLR-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1798:
---
Attachment: SOLR-1798.patch
New patch that fixes the cumulative stats by adding in an entry
[
https://issues.apache.org/jira/browse/SOLR-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1798.
Resolution: Fixed
committed.
Memory leak in FastLRUCache
[
https://issues.apache.org/jira/browse/SOLR-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12839419#action_12839419
]
Yonik Seeley commented on SOLR-1799:
Thanks Chris - this actually is sort of like
1 - 100 of 2570 matches
Mail list logo
