[
https://issues.apache.org/jira/browse/SOLR-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1186:
-
Attachment: SOLR-1186.patch
I shall commit this shortly
> parentdeltaQuery invoked on wrong entity
> ---
See http://hudson.zones.apache.org/hudson/job/Solr-trunk/814/changes
Hi Mark,
Yep, confirmed -- this is something compiler-related. This class:
carrot2-core/src/org/carrot2/core/test/assertions/Carrot2CoreAssertions.java:73:
has two methods with the same type erasure:
public static ClusterListAssertion assertThat(List actual)
public static DocumentListAssert
status command should do searcher.decref() in try{}finally{}
Key: SOLR-1187
URL: https://issues.apache.org/jira/browse/SOLR-1187
Project: Solr
Issue Type: Bug
Affects Versions:
[
https://issues.apache.org/jira/browse/SOLR-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul reassigned SOLR-1187:
Assignee: Noble Paul
> status command should do searcher.decref() in try{}finally{}
> --
[
https://issues.apache.org/jira/browse/SOLR-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1187:
-
Attachment: SOLR-1187.patch
> status command should do searcher.decref() in try{}finally{}
> -
[
https://issues.apache.org/jira/browse/SOLR-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul resolved SOLR-1187.
--
Resolution: Fixed
committed:779097
> status command should do searcher.decref() in try{}finally{}
> ---
TermVectorComponent Efficiency improvements
---
Key: SOLR-1188
URL: https://issues.apache.org/jira/browse/SOLR-1188
Project: Solr
Issue Type: Improvement
Reporter: Grant Ingersoll
[
https://issues.apache.org/jira/browse/SOLR-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved SOLR-1188.
---
Resolution: Fixed
Committed simple patch to override the two methods.
> TermVectorComponent E
I am seeing a behavior I have not seen before
With all standard queries (nothing custom etc), I will see a facet
list with items like:
* valueA (13)
* valueB (100)
* etc...
Then when I select valueA (that should have 13 results) I only get 2
results. When the index is optimized, it
Grant - I don't think you meant to remove Yonik's addition to
CHANGES.txt...
On May 27, 2009, at 8:34 AM, gsing...@apache.org wrote:
Author: gsingers
Date: Wed May 27 12:34:09 2009
New Revision: 779144
URL: http://svn.apache.org/viewvc?rev=779144&view=rev
Log:
SOLR-1188: Minor efficiency impr
Nope, I'll fix. I thought it merged.
On May 27, 2009, at 8:39 AM, Erik Hatcher wrote:
Grant - I don't think you meant to remove Yonik's addition to
CHANGES.txt...
On May 27, 2009, at 8:34 AM, gsing...@apache.org wrote:
Author: gsingers
Date: Wed May 27 12:34:09 2009
New Revision: 779144
U
On Wed, May 27, 2009 at 8:37 AM, Ryan McKinley wrote:
> I am seeing a behavior I have not seen before
>
> With all standard queries (nothing custom etc), I will see a facet list with
> items like:
> * valueA (13)
> * valueB (100)
> * etc...
>
> Then when I select valueA (that should have 13
from trunk sometime mid-morning yesterday
On May 27, 2009, at 8:46 AM, Yonik Seeley wrote:
On Wed, May 27, 2009 at 8:37 AM, Ryan McKinley
wrote:
I am seeing a behavior I have not seen before
With all standard queries (nothing custom etc), I will see a facet
list with
items like:
*
We've fixed the 1.5 compilation issue in Carrot2. As for this thing:
at
java.lang.ClassLoader.checkCerts(ClassLoader.java:792)
at java.lang.ClassLoader.preDefineClass(ClassLoader.java:504)
it most likely means classes from within the same package are picked from two
different locations
manifest info:
Specification-Version: 1.3.0.2009.05.26.09.08.22
Specification-Vendor: The Apache Software Foundation
Implementation-Title: org.apache.solr
Implementation-Version: 1.4-dev 778686 - ryan - 2009-05-26 09:08:22
On Wed, May 27, 2009 at 8:46 AM, Yonik Seeley
wrote:
> On Wed, May 27,
OK, it should be fixed now. There was a bug in the TermQuery set
generation code.
-Yonik
http://www.lucidimagination.com
On Wed, May 27, 2009 at 8:46 AM, Yonik Seeley
wrote:
> On Wed, May 27, 2009 at 8:37 AM, Ryan McKinley wrote:
>> I am seeing a behavior I have not seen before
>>
>> With
[
https://issues.apache.org/jira/browse/SOLR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-243:
-
Attachment: SOLR-243.patch
to trunk
> Create a hook to allow custom code to create custom IndexReaders
> -
[
https://issues.apache.org/jira/browse/SOLR-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1184:
--
Attachment: SOLR-1184.patch
> Add option to not reopen readers
>
>
>
Support basic auth
--
Key: SOLR-1189
URL: https://issues.apache.org/jira/browse/SOLR-1189
Project: Solr
Issue Type: New Feature
Components: replication (java)
Reporter: Matthew Gregg
Priority
Change the Search Order
---
Key: SOLR-1190
URL: https://issues.apache.org/jira/browse/SOLR-1190
Project: Solr
Issue Type: Wish
Environment: Java
Reporter: Asish Kumar Mohanty
Hi,
I m using solr 1.3
Anyone ever seen this? I am configuring solr with spring -- nothing
has changed recently.
It appears to be trying to open "DisMaxQParser" when the class is
actually "DismaxQParser"
Caused by: org.springframework.beans.BeanInstantiationException: Could
not instantiate bean class
[voyager.index.
[
https://issues.apache.org/jira/browse/SOLR-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713691#action_12713691
]
Yonik Seeley commented on SOLR-1190:
Solr doesn't maintain field order (neither does Luc
Looks like it was renamed
https://issues.apache.org/jira/browse/SOLR-1149
-Yonik
http://www.lucidimagination.com
On Wed, May 27, 2009 at 2:58 PM, Ryan McKinley wrote:
> Anyone ever seen this? I am configuring solr with spring -- nothing
> has changed recently.
>
> It appears to be trying to o
On Thu, May 28, 2009 at 12:28 AM, Ryan McKinley wrote:
> Anyone ever seen this? I am configuring solr with spring -- nothing
> has changed recently.
>
> It appears to be trying to open "DisMaxQParser" when the class is
> actually "DismaxQParser"
>
>
DismaxQParser was renamed to DisMaxQParser wi
[
https://issues.apache.org/jira/browse/SOLR-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713697#action_12713697
]
Erik Hatcher commented on SOLR-1190:
But, perhaps the fl parameter specified order shoul
NullPointerException in delta import
Key: SOLR-1191
URL: https://issues.apache.org/jira/browse/SOLR-1191
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Version
I think we should upgrade Lucene again since the index file format has changed:
https://issues.apache.org/jira/browse/LUCENE-1654
This also contains a fix for unifying the FieldCache and
ExtendedFieldCache instances.
$ svn diff -r r776177 CHANGES.txt
Index: CHANGES.txt
===
It was a problem with my svn update -- apparently it did not pick up
the case change. (not report any difference with svn diff)
When I did a clean checkout things worked ok.
On Wed, May 27, 2009 at 3:08 PM, Shalin Shekhar Mangar
wrote:
> On Thu, May 28, 2009 at 12:28 AM, Ryan McKinley wrote:
esshari wrote:
EG :if i search for "test",i got 100 results.In my schema.xml i have a field
"permission".It contains yes or no.If a user whom have limited permission to
some results.so for that result i will mark as "no" while indexing.When
search "test" the result displayed should be 95.That is
On Thu, May 28, 2009 at 2:28 AM, Yonik Seeley wrote:
> I think we should upgrade Lucene again since the index file format has
> changed:
> https://issues.apache.org/jira/browse/LUCENE-1654
>
>
+1
--
Regards,
Shalin Shekhar Mangar.
I wonder if it would be useful to commit Lucene's CHANGES.txt into Solr along
with Solr jars. It would then be very easy to tell what changed in Lucene
since the version Solr has and the current version of Lucene (or some newer
released version, if we were able to be behind).
Otis
--
Sematex
[
https://issues.apache.org/jira/browse/SOLR-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-1051.
-
Resolution: Fixed
Fix Version/s: 1.4
Committed revision 779423.
Thanks Nin
[
https://issues.apache.org/jira/browse/SOLR-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1106:
-
Attachment: SOLR-1106.patch
The adminhandler attribute must be persisted back to solr.xml
> Pluggable Cor
[
https://issues.apache.org/jira/browse/SOLR-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713882#action_12713882
]
Noble Paul commented on SOLR-1106:
--
committed : 779439
> Pluggable CoreAdminHandler (Acti
[
https://issues.apache.org/jira/browse/SOLR-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-920:
Attachment: SOLR-920.patch
the attribute is not persisted back to solr.xml
> Cache and reuse IndexSchema
> -
[
https://issues.apache.org/jira/browse/SOLR-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-920:
Attachment: (was: SOLR-920.patch)
> Cache and reuse IndexSchema
> ---
>
>
[
https://issues.apache.org/jira/browse/SOLR-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-920:
Attachment: SOLR-920.patch
> Cache and reuse IndexSchema
> ---
>
> Ke
38 matches
Mail list logo
