I'm fine with 1.6 as a min requirement... but i imagine others have
different opinions :)
On Wed, Apr 14, 2010 at 2:53 PM, Yonik Seeley
yo...@lucidimagination.com wrote:
Yes, it requires that Solr in general is compiled with Java6. We
should make our lives easier and make Java6 a Solr
(perhaps more appropriate on solr-user@)
It sounds like you want to make a MathML filter? Check out the
analyzer packages...
http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters
simple example:
Hi Anders-
see comments below...
Two weeks ago I created a JIRA issue (
https://issues.apache.org/jira/browse/SOLR-1834) involving document level
security in Apache Solr and submitted a patch containing a search component
that can be seen as a starting point for making Solr handle document
why not just d...@lucene.apache.org?
On Mon, Mar 22, 2010 at 11:44 AM, Grant Ingersoll gsing...@apache.org wrote:
Shall we merge the dev mailing lists? This should reduce the cross-posting
and can be completely automated (other than you may have to update your
client-side filters) and was
Logistically, how would this work?
would d...@lucene.apache.org be an alias for java-dev and solr-dev? or
a whole new list?
Would people need to subscribe to it, or would you already be on the
list if you were on java/solr dev? If we are on both lists, do we get
two copies of every message?
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...
What about something general like:
https://svn.apache.org/repos/asf/lucene/dev
or
https://svn.apache.org/repos/asf/lucene/project
ryan
On Mon, Mar 22, 2010 at 2:02 PM,
I don't see a compelling reason to go to 3.1. It is going to be very
confusing for users (when did 3.0 come out? Did I miss it?) At least
when MS Word jumped from 2.0 to 6.0 it wasn't to a minor version (i.e.
6.1). 2.0 seems reasonable, as does 1.5. Although 2.0 would be a good
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
initialized by index, but that became moot with the CoreContainer
stuff.
ryan
On Jan 12, 2010, at 5:45 AM, Erik Hatcher wrote:
Hey gang,
I'd like to put an image and link to our LucidWorks for Solr
Certified Distro Reference Guide on the Solr front page, and
wondering if there were any objections.
To toss out my only objection with my Apache hat on (yes, I'm
On Jan 12, 2010, at 10:59 AM, markrmil...@apache.org wrote:
Author: markrmiller
Date: Tue Jan 12 15:59:01 2010
New Revision: 898393
URL: http://svn.apache.org/viewvc?rev=898393view=rev
Log:
merge up to r898346
dooh, sorry mark -- hope that was not too difficult.
thanks
ryan
[
https://issues.apache.org/jira/browse/SOLR-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798797#action_12798797
]
Ryan McKinley commented on SOLR-1715:
-
this would also be a good way to 'punt' complex
[
https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-1602:
---
Assignee: Ryan McKinley (was: Noble Paul)
Refactor SOLR package structure to include
[
https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799059#action_12799059
]
Ryan McKinley commented on SOLR-1602:
-
I made a few changes to /trunk, but we are still
[
https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12797677#action_12797677
]
Ryan McKinley commented on SOLR-1602:
-
| .Besides which: even if it's just an example
[
https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12797678#action_12797678
]
Ryan McKinley commented on SOLR-1602:
-
Nobel, this issue is assigned to you? Do you
can you submit a patch to JIRA?
On Jan 7, 2010, at 10:23 AM, Attila Babo wrote:
While inserting a large pile of documents using
StreamingUpdateSolrServer I've found a race condition as all Runner
instances stopped while the blocking queue was full. The attached
patch solves the problem, to
[
https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12797227#action_12797227
]
Ryan McKinley commented on SOLR-1602:
-
Hey Chris-
Don't worry about putting up a patch
[
https://issues.apache.org/jira/browse/SOLR-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796280#action_12796280
]
Ryan McKinley commented on SOLR-1568:
-
I'm torn on this also...
The function query
[
https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796285#action_12796285
]
Ryan McKinley commented on SOLR-1602:
-
In an effort to get some resolution here
[
https://issues.apache.org/jira/browse/SOLR-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796352#action_12796352
]
Ryan McKinley commented on SOLR-1568:
-
{quote}
could be written as
{code}
fq={!sfilt f
DocFrequencyValueSource
---
Key: SOLR-1694
URL: https://issues.apache.org/jira/browse/SOLR-1694
Project: Solr
Issue Type: New Feature
Components: search
Reporter: Ryan McKinley
Priority
[
https://issues.apache.org/jira/browse/SOLR-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-1694:
Attachment: SOLR-1694-DocFrequencyValueSource.patch
This is a first draft, it gets the DF
[
https://issues.apache.org/jira/browse/SOLR-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796079#action_12796079
]
Ryan McKinley commented on SOLR-1694:
-
I don't know if folks think this is generally
[
https://issues.apache.org/jira/browse/SOLR-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12795737#action_12795737
]
Ryan McKinley commented on SOLR-1690:
-
I have been using it to have structured data
[
https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12795341#action_12795341
]
Ryan McKinley commented on SOLR-1602:
-
Sounds fine... except for the back compatibility
[
https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12795352#action_12795352
]
Ryan McKinley commented on SOLR-1602:
-
| I'm a fan of number 2, and I'd venture to guess
Here's what you're voting on:
[ x] Yes, move forward with SOLR-1602 with the plan proposed above
[ ] No, don't move forward with SOLR-1602 because...
I'll leave the vote open for 72 hours. Votes from SOLR committers are
binding, but everyone is welcome to voice your opinion.
Not to throw
and Analysis
Reporter: Ryan McKinley
Priority: Minor
Sometimes it is nice to group structured data into a single field.
This (rough) patch, takes JSON input and indexes tokens based on the key values
pairs in the json.
For example, the text:
{code}
{ hello: world, rank:5 }
{code
[
https://issues.apache.org/jira/browse/SOLR-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-1690:
Attachment: SOLR-1690-JSONKeyValueTokenizerFactory.patch
Here is a simple JSON tokenizer. No tests
[
https://issues.apache.org/jira/browse/SOLR-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-1690:
Attachment: noggit-1.0-A1.jar
This tokenizer uses noggit
http://svn.apache.org/repos/asf/labs
[
https://issues.apache.org/jira/browse/SOLR-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-1690:
Description:
Sometimes it is nice to group structured data into a single field.
This (rough) patch
[
https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12795428#action_12795428
]
Ryan McKinley commented on SOLR-1602:
-
| the patch does not apply. iis it not updated
On Nov 25, 2009, at 11:30 AM, Chris Hostetter wrote:
: The point being: it's all been very informat up to now -- and
that's
: probably for the best. policies should evolve over time based
on real
: world situations that come up, and we're still in the process of
doing
: that.
:
:
[
https://issues.apache.org/jira/browse/SOLR-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781282#action_12781282
]
Ryan McKinley commented on SOLR-1589:
-
| But SolrException != HttpRequestException
switching back to solr-dev... sorry for spinning off that thread...
What is a serious change that would warrant a bump in your opinion?
for example:
- config overhaul. detangle the XML from the components. perhaps
using
spring.
This is already done. No components read config from xml
[
https://issues.apache.org/jira/browse/SOLR-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12779726#action_12779726
]
Ryan McKinley commented on SOLR-1568:
-
| I think the best way is to maintain the code
so I don't think any sort of
generic cache is needed for geo.
Agreed, no generic cache for geo. Was thinking about a generic
cache for function calculations.
I think even more generally would be good -- an easy way to share
calculations between anything in the request cycle:
And a big thank you to Grant for managing this release!
thanks Grant
On Nov 10, 2009, at 10:38 AM, Grant Ingersoll wrote:
Feel free to move forward on 1.5...
Announcement will be sent out shortly on 1.4. Good work everyone!
-Grant
+1
On Nov 6, 2009, at 2:25 PM, Yonik Seeley wrote:
+1 for releasing these artifacts:
1cc3783316aa1f95ba5e250a4c1d0451 apache-solr-1.4.0.tgz
8da9395565736499f80542c8d05b3854 apache-solr-1.4.0.zip
-Yonik
http://www.lucidimagination.com
On Fri, Nov 6, 2009 at 1:28 PM, Grant Ingersoll
+1
On Oct 30, 2009, at 12:40 PM, Grant Ingersoll wrote:
OK, take 3: http://people.apache.org/~gsingers/solr/1.4.0/
On Oct 30, 2009, at 8:10 AM, Grant Ingersoll wrote:
Got it. Will upload shortly.
On Oct 29, 2009, at 8:33 PM, Yonik Seeley wrote:
On Thu, Oct 29, 2009 at 7:36 PM, Yonik
+1
Integrated with my app, and things work well. (windows vista)
Ran examples and everything worked as expected. (Mac OSX)
On Oct 27, 2009, at 10:07 PM, Grant Ingersoll wrote:
OK, new artifacts are up.
On Oct 27, 2009, at 9:51 PM, Chris Hostetter wrote:
: By other issues, I mean the
On Oct 28, 2009, at 9:12 PM, Nicholas Letourneau wrote:
Not sure who gets a vote,
Everyone gets to vote -- officially some votes are 'binding' but in
practice this does not really matter.
The more feedback there is, the more confidence we have that things
are good (or need fixed)
On Oct 26, 2009, at 4:00 PM, Grant Ingersoll wrote:
So, just to clarify, here's the plan as I understand it:
1. Put up a 1.4.0 RC today w/ 2.9.1-RC2
2. Commence vote on 1.4.0
3. Once 2.9.1 is finalized, replace in Solr and generate final
artifacts
We also must make sure the maven pom.xml
Also, not sure what the policy is on voting on files where the pom
still needs to change..
http://people.apache.org/~gsingers/solr/1.4.0/maven/org/apache/solr/solr-core/1.4.0/solr-core-1.4.0.pom
points to:
dependency
groupIdorg.apache.lucene/groupId
artifactIdlucene-analyzers/artifactId
I've been testing with jetty 7.0.0.v20091005, and everything works
good so far..
On Oct 25, 2009, at 3:59 PM, Yonik Seeley wrote:
If all goes well in lucene-land 2.9.1 should start a vote on Monday
sometime...
I've recently tested the latest stable Jetty (6.1.21) ... so we can
avoid some
I'm looking through a bunch of logs that have:
UpdateRequestProcessor - {add=[aa, bb, cc, dd, ee, ff, gg, hh, ...(142 more)]}
Would it be more reasonable to say: 150 total rather then make you
count the previous 8?
kinda stupid, but i guess this is what drives you nuts while chasing
real
[
https://issues.apache.org/jira/browse/SOLR-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-1512:
Attachment: SOLR-1512-luke.patch
pointing to luke 0.9.9
point build.xml to luke 0.9.9
[
https://issues.apache.org/jira/browse/SOLR-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-1512.
-
Resolution: Fixed
point build.xml to luke 0.9.9
thanks for pointing this out. Check: SOLR-1512, now fixed in trunk
thanks
ryan
On Oct 15, 2009, at 10:58 AM, Colin Hynes wrote:
I just thought I'd toss a note out that in the main build.xml it's
fetching a outdated vesions of luke(0.9.1) and lucene(2.4).
For the solr 1.4 release, that
[
https://issues.apache.org/jira/browse/SOLR-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12765582#action_12765582
]
Ryan McKinley commented on SOLR-1510:
-
we went back and forth on this one for a while
I'm on it! At least it is easy...
On Oct 10, 2009, at 3:13 PM, Grant Ingersoll wrote:
Down to 1:
https://issues.apache.org/jira/secure/BrowseVersion.jspa?id=12310230versionId=12313351showOpenIssuesOnly=true
Things are looking good for Monday. I'd encourage everyone to check
out trunk
[
https://issues.apache.org/jira/browse/SOLR-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-1497.
-
Resolution: Fixed
solrjs was removed in rev 824396
This can be pulled from subversion history
Looks like we are down to zero issues:
https://issues.apache.org/jira/secure/BrowseVersion.jspa?id=12310230versionId=12313351showOpenIssuesOnly=true
Remove solrjs from svn -- point docs to AJAX Solr
-
Key: SOLR-1497
URL: https://issues.apache.org/jira/browse/SOLR-1497
Project: Solr
Issue Type: Task
Reporter: Ryan McKinley
[
https://issues.apache.org/jira/browse/SOLR-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-1294.
-
Resolution: Won't Fix
With SOLR-1497, solrjs devlopment will move to AJAX solr on github
SolrJS
[
https://issues.apache.org/jira/browse/SOLR-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-1434.
-
Resolution: Fixed
Fix Version/s: 1.4
See SOLR-1497
Evaluate Including SolrJS
[
https://issues.apache.org/jira/browse/SOLR-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12762848#action_12762848
]
Ryan McKinley commented on SOLR-1294:
-
Looking over it, it seems interesting... what
[
https://issues.apache.org/jira/browse/SOLR-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12762860#action_12762860
]
Ryan McKinley commented on SOLR-1294:
-
sweet. If AJAX-Solr is Apache licensed, then I
[
https://issues.apache.org/jira/browse/SOLR-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12762864#action_12762864
]
Ryan McKinley commented on SOLR-1294:
-
In your 'COPYRIGHT.txt' file, it says:
[panel
[
https://issues.apache.org/jira/browse/SOLR-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12762864#action_12762864
]
Ryan McKinley edited comment on SOLR-1294 at 10/6/09 9:17 PM
I don't think solrjs should hold up the 1.4 release.
Since this issue was last discussed, James McKinney has licensed AJAX
Solr (a solrjs fork) under Apache MIT
http://github.com/evolvingweb/AJAX-Solr/blob/master/COPYRIGHT.txt
It seems like this has good support and gets the on-going
[
https://issues.apache.org/jira/browse/SOLR-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12762866#action_12762866
]
Ryan McKinley commented on SOLR-1294:
-
excellent -- thank you
SolrJS/Javascript client
[
https://issues.apache.org/jira/browse/SOLR-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-1472:
Attachment: SOLR-1472-maven-cleanup.patch
deleting the solr specific maven files.
I will go ahead
[
https://issues.apache.org/jira/browse/SOLR-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-1472.
-
Resolution: Fixed
committed in rev819835
When we want to use lucene snapshots again, we can get
I just discussed this off-line with Matthias. It does not look like
he has the time to give this much attention now. (nor do I)
We agreed that the best steps forward are to:
1. Support the Drupal guys GPL port
2. Archive the solrjs code to solrstuff.org
3. Yank solrjs from apache svn (and 1.4
the Drupal guys and others to submit their changes?
Perhaps by then Matthias or you or someone else will have stepped up.
On Sep 28, 2009, at 7:27 PM, Ryan McKinley wrote:
I just discussed this off-line with Matthias. It does not look like
he has the time to give this much attention now. (nor do I
[
https://issues.apache.org/jira/browse/SOLR-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-1472:
Summary: upgrade maven poms to reference lucene 2.9 artifacts rather than
solr-lucene artifacts
: Solr
Issue Type: Task
Affects Versions: 1.4
Reporter: Ryan McKinley
Assignee: Ryan McKinley
Priority: Blocker
Fix For: 1.4
Currently, the solr pom.xml files reference solr-lucene jar files. Rather then
reference the solr jars, we
: SOLR-1294 SolrJS/Javascript client fails in IE8! Unassigned
:
: I have concerns about this client library being included at all
in Solr, as
: I don't see anyone taking it up for maintenance. I raised
concerns on the
: main issue with no response and likewise with this one. Patch
[
https://issues.apache.org/jira/browse/SOLR-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-1294:
---
Assignee: Ryan McKinley
SolrJS/Javascript client fails in IE8
[
https://issues.apache.org/jira/browse/SOLR-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12754386#action_12754386
]
Ryan McKinley commented on SOLR-1424:
-
no dice. with:
{code}
$ svn diff
Index: common
[
https://issues.apache.org/jira/browse/SOLR-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-1424:
---
Assignee: Ryan McKinley
yup, that does it... I will commit shortly
ant generate-maven
[
https://issues.apache.org/jira/browse/SOLR-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-1424:
Attachment: SOLR-1424.patch
ant generate-maven-artifacts fails on windows
[
https://issues.apache.org/jira/browse/SOLR-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-1424.
-
Resolution: Fixed
Fix Version/s: 1.4
ant generate-maven-artifacts fails on windows
have not tried it yet but we should certainly upgrade.
the more testing the better!
On Aug 28, 2009, at 2:54 PM, Grant Ingersoll wrote:
Anyone tried out the new Lucene RC2 in Solr yet? Should we upgrade
to it?
:
I'll take a look. Have you tried a diff. version of Maven?
On Aug 24, 2009, at 3:09 PM, Ryan McKinley wrote:
Anyone else seeing this:
$ ant generate-maven-artifacts
...
...
BUILD FAILED
c:\workspace\apache\solr\build.xml:741: The following error occurred
while executing this line:
c:\workspace
[
https://issues.apache.org/jira/browse/SOLR-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12747012#action_12747012
]
Ryan McKinley commented on SOLR-1377:
-
Without objection... I will commit this soon
[
https://issues.apache.org/jira/browse/SOLR-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-1377.
-
Resolution: Fixed
Force TokenizerFactory to create a Tokenizer rather then TokenStream
Anyone else seeing this:
$ ant generate-maven-artifacts
...
...
BUILD FAILED
c:\workspace\apache\solr\build.xml:741: The following error occurred
while executing this line:
c:\workspace\apache\solr\common-build.xml:261: Failed to copy
:
Ryan McKinley wrote:
Ahh, I see:
Tokenizer extends TokenStream
So if this is going to break everything that implements TokenStream
rather then Tokenizer, it seems we should change the
TokenizerFactory
API from:
public Tokenizer create( Reader input )
rather then:
public TokenStream create
[
https://issues.apache.org/jira/browse/SOLR-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-1057:
Attachment: SOLR-1057-PathTokenizerFactory.patch
updated to use reusable token stuff
Just updated to /trunk and am now seeing this exception:
Caused by: org.apache.solr.client.solrj.SolrServerException:
java.lang.ClassCastException:
xxx.solr.analysis.JSONKeyValueTokenizerFactory$1 cannot be cast to
org.apache.lucene.analysis.Tokenizer
at
Actually I think there may be something wrong here.
BaseTokenizerFactory does not make a Tokenizer, it creates a
TokenStream, so it should never be cast to Tokenizer
My custom TokenizerFactory now looks the same as:
o.a.s.analysis.PatternTokenizerFactory
Not sure what to look at next...
On Aug 21, 2009, at 10:49 AM, Yonik Seeley wrote:
On Fri, Aug 21, 2009 at 10:33 AM, Ryan McKinleyryan...@gmail.com
wrote:
Actually I think there may be something wrong here.
BaseTokenizerFactory does not make a Tokenizer, it creates a
TokenStream, so it should never be cast to Tokenizer
Ahh, I see:
Tokenizer extends TokenStream
So if this is going to break everything that implements TokenStream
rather then Tokenizer, it seems we should change the TokenizerFactory
API from:
public Tokenizer create( Reader input )
rather then:
public TokenStream create( Reader input );
Feature
Components: Analysis
Reporter: Ryan McKinley
Assignee: Ryan McKinley
Fix For: 1.4
The new token reuse classes require that they are created with a Tokenizer.
The solr TokenizerFactory interface currently makes a TokenStream.
Although
[
https://issues.apache.org/jira/browse/SOLR-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-1377:
Attachment: SOLR-1377-Tokenizer.patch
Here is a patch that:
1. Changes the TokenizerFactory
[
https://issues.apache.org/jira/browse/SOLR-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12746287#action_12746287
]
Ryan McKinley commented on SOLR-1377:
-
Is reset gaurenteed to be called on the same
On Aug 18, 2009, at 10:01 AM, Grant Ingersoll wrote:
On Aug 18, 2009, at 9:49 AM, Ryan McKinley wrote:
Also, I'm thinking about having a real simple interface that
would allow
for, when materializing the Fields, to pass in something like a
DocumentModifier, which would basically get
[
https://issues.apache.org/jira/browse/SOLR-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-705:
---
Fix Version/s: (was: 1.4)
1.5
Moving this issue to 1.5 so that the details
Ya, I like this idea.
Adding a meta field is OK, but it may just be kicking the can. Also
implementation wise, it works well when you have a SolrDocument, but
when directly using DocList, it gets a bit messy.
https://issues.apache.org/jira/browse/SOLR-705
Also with adding a meta field,
[
https://issues.apache.org/jira/browse/SOLR-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-868.
Resolution: Fixed
My apologies, this was actually resolved months ago! (and solrjs is now in
http
[
https://issues.apache.org/jira/browse/SOLR-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-705:
--
Assignee: Ryan McKinley
Distributed search should optionally return docID-shard map
[
https://issues.apache.org/jira/browse/SOLR-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12739076#action_12739076
]
Ryan McKinley commented on SOLR-705:
I'll take this one on for 1.4...
I incorporate hoss
[
https://issues.apache.org/jira/browse/SOLR-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737649#action_12737649
]
Ryan McKinley commented on SOLR-1320:
-
dooh. thanks erik
[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12733900#action_12733900
]
Ryan McKinley commented on SOLR-773:
Wow, this issue just keeps growing! We need
[
https://issues.apache.org/jira/browse/SOLR-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12729462#action_12729462
]
Ryan McKinley commented on SOLR-1171:
-
thanks hoss!
dynamic field name with spaces
Just started getting this error with a recent update:
Caused by: java.lang.IllegalStateException: Illegal sort type: 2
at org.apache.lucene.search.SortField.getComparator(SortField.java:492)
at
. Could be the recent changes
to Solr for LUCENE-1483 - auto now has to be resolved before using the
collector, ie using int autotype = SortField.detectFieldType(reader,
fieldname);
I remember this changing but not the exact details.
Probably Solr is not doing this though.
- Mark
Ryan
Reporter: Ryan McKinley
Assignee: Ryan McKinley
Fix For: 1.4
Currently the LukeRequestHandler is calling:
int docCount = searcher.numDocs( q, matchAllDocs );
followed by:
DocList ds = searcher.getDocList( q, (Query)null, (Sort)null, 0, 1 );
to get the doc count
1 - 100 of 1482 matches
Mail list logo
