How do you all feel about forcing the fields in SolrDocument to be
Serializable?
from
private MapString,Object _fields = null;
to:
private MapString,Serializable _fields = null;
likewise with SolrInputField?
from:
Object value = null;
to
Serializable value = null;
Everything we are
Ideally we don't need to.
However, we do need to convert things like DocList to
SolrDocumentList, also the Map/List representation should match what
happens *if* it did go via HTTP. That is, if a handler adds a
LinkedHashSet to the response, the client does not know that -- it
just
[
https://issues.apache.org/jira/browse/SOLR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-641.
Resolution: Fixed
Fix Version/s: 1.3
expose EmbeddedSolrServer response parsing
[
https://issues.apache.org/jira/browse/SOLR-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12615122#action_12615122
]
Ryan McKinley commented on SOLR-614:
If I understood the discussion on the dev list
[
https://issues.apache.org/jira/browse/SOLR-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-638:
---
Description: We need to provide some way for cores to access other cores
registered within MultiCore
[
https://issues.apache.org/jira/browse/SOLR-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-638:
---
Attachment: SOLR-638.patch
Looks good -- I made two small changes:
1. MultiCore is now final
[
https://issues.apache.org/jira/browse/SOLR-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-638.
Resolution: Fixed
Fix Version/s: 1.3
Enable access to MultiCore from SolrCore
[
https://issues.apache.org/jira/browse/SOLR-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614760#action_12614760
]
Ryan McKinley commented on SOLR-561:
I just committed SOLR-638 -- I think this patch
[
https://issues.apache.org/jira/browse/SOLR-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614767#action_12614767
]
Ryan McKinley commented on SOLR-638:
You talking about the reloadCore() method
I'm trying to write a search component that queries another core.
This pointed out that there is no way to access MultiCore outside of
SolrDispatchFilter.
If we were using spring, we could easily pass that reference into the
component. Without it, I think the best option is to add a
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614337#action_12614337
]
Ryan McKinley commented on SOLR-350:
it looks like dataDir option was removed from
[
https://issues.apache.org/jira/browse/SOLR-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614340#action_12614340
]
Ryan McKinley commented on SOLR-638:
I like that idea.
Allow static access
[
https://issues.apache.org/jira/browse/SOLR-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-637.
Resolution: Invalid
multicore ignores -Dsolr.data.dir=dir
[
https://issues.apache.org/jira/browse/SOLR-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614371#action_12614371
]
Ryan McKinley commented on SOLR-637:
{panel}
Is the name of the core available
[
https://issues.apache.org/jira/browse/SOLR-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12613950#action_12613950
]
Ryan McKinley commented on SOLR-485:
Is the concern here not to break compatibility
[
https://issues.apache.org/jira/browse/SOLR-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614010#action_12614010
]
Ryan McKinley commented on SOLR-485:
I think we should deprecate it and remove it from
[
https://issues.apache.org/jira/browse/SOLR-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614111#action_12614111
]
Ryan McKinley commented on SOLR-637:
Assuming your solrconfig.xml includes
looking over some of the spellchecking stuff...
One thing that sticks out as strange is that the component and the
handler have different params!
The handler uses:
sp.query.accuracy
sp.query.onlyMorePopular
...
http://wiki.apache.org/solr/SpellCheckerRequestHandler
while the component
I'm raising my objection to -1 for the updated syntax. Let's make
that a
post 1.3 (2.0, is my suggestion) feature.
Users tend to stick to a released version for very long. A lot of
users (we too) still use Solr 1.2. That means we are going to see this
syntax for atleast another year after
I have been using 6.1.11 also.
I think it should be safe to upgrade before 1.3
On Jul 12, 2008, at 2:17 PM, Otis Gospodnetic wrote:
I'm pro 6.1.11. I've used it on several occasions now and haven't
seen any problems with it.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr -
[
https://issues.apache.org/jira/browse/SOLR-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12612527#action_12612527
]
Ryan McKinley commented on SOLR-620:
perhaps look at convrting the DocList
[
https://issues.apache.org/jira/browse/SOLR-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12612697#action_12612697
]
Ryan McKinley commented on SOLR-501:
Has anyone looked at this? Any reason
[
https://issues.apache.org/jira/browse/SOLR-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-501:
--
Assignee: Ryan McKinley
/admin/analysis.jsp does not decode input string as UTF-8 sequence
[
https://issues.apache.org/jira/browse/SOLR-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-501:
---
Fix Version/s: 1.3
/admin/analysis.jsp does not decode input string as UTF-8 sequence
Register copyField at runtime
-
Key: SOLR-619
URL: https://issues.apache.org/jira/browse/SOLR-619
Project: Solr
Issue Type: New Feature
Reporter: Ryan McKinley
Assignee: Ryan McKinley
[
https://issues.apache.org/jira/browse/SOLR-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-605.
Resolution: Fixed
Programatically register SolrEventListeners
[
https://issues.apache.org/jira/browse/SOLR-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-619:
---
Attachment: SOLR-619-RuntimeSchema.patch
This patch moves the copyField registration out of a for loop
[
https://issues.apache.org/jira/browse/SOLR-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611296#action_12611296
]
Ryan McKinley commented on SOLR-605:
true -- likewise with SOLR-619 -- however all
[
https://issues.apache.org/jira/browse/SOLR-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611321#action_12611321
]
Ryan McKinley commented on SOLR-605:
bq. w/o opening up the can of worms of a mutable
[
https://issues.apache.org/jira/browse/SOLR-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611333#action_12611333
]
Ryan McKinley commented on SOLR-605:
check the [existing
javadocs|http
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609968#action_12609968
]
Ryan McKinley commented on SOLR-350:
thanks for finding this Markus!
fixed in rev 673430
[
https://issues.apache.org/jira/browse/SOLR-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-605:
---
Attachment: SOLR-605-RegisterEventListeners.patch
this adds
{code:java}
UpdateHandler.java:
void
[
https://issues.apache.org/jira/browse/SOLR-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608646#action_12608646
]
Ryan McKinley commented on SOLR-607:
Perhaps this is not the place to discuss
How do you all feel about exposing access to the commit/optimize
callbacks in UpdateHandler? Perhaps adding the functions:
void registerCommitCallback( SolrEventListener );
void registerCommitCallback( SolrEventListener );
and/or maybe:
CollectionSolrEventListener getCommitCollbacks();
[
https://issues.apache.org/jira/browse/SOLR-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607484#action_12607484
]
Ryan McKinley commented on SOLR-536:
ok, I put it back in rev 671037
Automatic binding
[
https://issues.apache.org/jira/browse/SOLR-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-602:
--
Assignee: Ryan McKinley
Method chaining in SolrQuery
[
https://issues.apache.org/jira/browse/SOLR-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607475#action_12607475
]
Ryan McKinley commented on SOLR-536:
hymmm, after using this for a bit, i'm not sure we
[
https://issues.apache.org/jira/browse/SOLR-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607477#action_12607477
]
Ryan McKinley commented on SOLR-536:
i removed it in rev671034 -- with SolrServer
On Jun 5, 2008, at 7:41 AM, Andrew Savory wrote:
Hi,
2008/6/4 Andrew Savory [EMAIL PROTECTED]:
I see from http://issues.apache.org/jira/browse/SOLR-19 that some
tentative work has been done on mavenisation of solr, and from
https://issues.apache.org/jira/browse/SOLR-586 that discussion of
[
https://issues.apache.org/jira/browse/SOLR-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12603136#action_12603136
]
Ryan McKinley commented on SOLR-486:
bq. or we will have to modify
+num = 234;
+ //? why 1?
+ // assertEquals( 0, BitUtil.ntz(num) );
+ // assertEquals( 0, BitUtil.ntz2(num) );
+ // assertEquals( 0, BitUtil.ntz3(num) );
+ }
Any idea why the answer is 1? the docs say (only works for x!=0)
[
https://issues.apache.org/jira/browse/SOLR-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12602647#action_12602647
]
Ryan McKinley commented on SOLR-536:
I think we should remove it from QueryResponce
[
https://issues.apache.org/jira/browse/SOLR-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-536.
Resolution: Fixed
Fix Version/s: 1.3
This was commited with some minor changes
[
https://issues.apache.org/jira/browse/SOLR-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12602733#action_12602733
]
Ryan McKinley commented on SOLR-536:
done. thanks
Automatic binding of results
[
https://issues.apache.org/jira/browse/SOLR-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-493:
---
Attachment: SOLR-493-OldAdminFile.patch
This patch checks for admin/gettableFiles and adds
oops, this got sent without a comment
Should be added missing @since tags to new solrj classes
On Jun 5, 2008, at 2:16 PM, [EMAIL PROTECTED] wrote:
Author: ryan
Date: Thu Jun 5 11:16:44 2008
New Revision: 663693
URL: http://svn.apache.org/viewvc?rev=663693view=rev
Log: (empty)
Modified:
[
https://issues.apache.org/jira/browse/SOLR-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12602740#action_12602740
]
Ryan McKinley commented on SOLR-486:
Should we make this the default parser
Any reason to keep the package: org.apache.solr.util.test?
I think we discussed deleting it before 1.2, but never got around to
it. Nothing is derecated, but it is also not used anywhere...
[
https://issues.apache.org/jira/browse/SOLR-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12602874#action_12602874
]
Ryan McKinley commented on SOLR-560:
I removed this from the 1.3 list...
Hopefully we
[
https://issues.apache.org/jira/browse/SOLR-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-536:
---
Attachment: SOLR-536.patch
Here is an updated version of the patch that also lets you use the same
[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12601614#action_12601614
]
Ryan McKinley commented on SOLR-139:
the biggest reason this patch won't work
On May 26, 2008, at 12:30 PM, Chris Hostetter wrote:
: content). Didn't we look into converting to Confluence at one
point in time?
Ryan was looking into it, and had an example up ... but i think
there may
have been a momentum issue (it was right before xmas as i recall).
Ryan?
I
Hymm, I guess folks aren't coming out of the woodwork to vote for this
one.
Wicket recently had a poll with ~100 votes cast:
http://www.nabble.com/Re%3A--vote--Release-1.4-with-only-generics-and-stop-support-for-1.3-p16220947.html
So I'm not sure where that leaves us. Unless Grant feels
On May 22, 2008, at 5:59 PM, Otis Gospodnetic wrote:
I agree. Lots of what Jason is doing looks good, but like I pointed
the other day, needs a lot more explanation, at least for dense
people like moi. My guess is, if we want to be aggressive with 1.3,
that none of Jason's stuff will
I don't know exactly what Hoss has in mind, but for one thing it would
mean we would need to support this in the future.
In general, changes like this get discussed for a while -- flushing
out any potential implications -- before they get added. The process
can be a bit annoying (and
[
https://issues.apache.org/jira/browse/SOLR-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-467.
Resolution: Fixed
Remove 'core' options from solrj
[
https://issues.apache.org/jira/browse/SOLR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-446.
Resolution: Fixed
TextResponseWriter should be able to work with SolrDocument
[
https://issues.apache.org/jira/browse/SOLR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-281.
Resolution: Fixed
I'll mark this issue as fixed -- I'm not sure why it was still open, the
reason
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-350.
Resolution: Fixed
Fix Version/s: 1.3
Manage Multiple SolrCores
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-350:
--
Assignee: Ryan McKinley
Manage Multiple SolrCores
[
https://issues.apache.org/jira/browse/SOLR-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-312:
--
Assignee: Ryan McKinley
create solrj javadoc in build.xml
[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-139:
---
Fix Version/s: (was: 1.3)
Support updateable/modifiable documents
[
https://issues.apache.org/jira/browse/SOLR-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-493:
--
Assignee: Ryan McKinley
/admin/file links don't work with legacy configs
[
https://issues.apache.org/jira/browse/SOLR-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595766#action_12595766
]
Ryan McKinley commented on SOLR-308:
if you are using trunk (the nightly builds, not 1.2
[
https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595406#action_12595406
]
Ryan McKinley commented on SOLR-567:
I take it this is related to SOLR-564? (oceansearch
[
https://issues.apache.org/jira/browse/SOLR-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-560:
---
Attachment: SOLR-560-slf4j.patch
Convert JDK logging to SLF4J
[
https://issues.apache.org/jira/browse/SOLR-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-560:
---
Attachment: slf4j-jdk14-1.5.0.jar
Convert JDK logging to SLF4J
[
https://issues.apache.org/jira/browse/SOLR-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-560:
---
Attachment: slf4j-api-1.5.0.jar
Convert JDK logging to SLF4J
[
https://issues.apache.org/jira/browse/SOLR-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594136#action_12594136
]
Ryan McKinley commented on SOLR-560:
I attached a quick patch to convert to SLF4j. I
If a large subset of the community is in favor of moving away from JUL
towards some alternative (and I'm not sure that's true),
Perhaps we should take a poll on solr-user? On the dev list, I there
are a few strong opinions, but I suspect most people don't really care
(as long as it
I think contrib is a good thing to consider. The DataImportHandler is
impressive, but huge. Although I think loading data from SQL should
be a 'core' feature, it makes sense to extract it.
As for packaging, 'contrib' features could be .jars that get dropped
into the lib directory, or
[ ] Keep solr logging as is. (JUL)
[X] Convert solr logging to SLF4J
In an effort to put this thread to rest with some sense of closure,
perhaps we could take a poll of our options:
[ ] Keep solr logging as is. (JUL)
[ ] Convert solr logging to SLF4J
I think the arguments for each option are:
JUL:
+ it is standard and *should* work everywhere
+ no
[
https://issues.apache.org/jira/browse/SOLR-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591672#action_12591672
]
Ryan McKinley commented on SOLR-549:
This solves the how do I use log4j in solr problem
?
--Noble
On Thu, Apr 10, 2008 at 3:03 AM, Ryan McKinley [EMAIL PROTECTED]
wrote:
yes, in an early version of solrj, I had an annotation -
SolrDocument
implementation. It also had a hibernate connection inspired by
compass
(http://www.compass-project.org/) -- it got tossed in an effort
[
https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586136#action_12586136
]
Ryan McKinley commented on SOLR-84:
---
I kinda like the sun image from:
http
[
https://issues.apache.org/jira/browse/SOLR-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585256#action_12585256
]
Ryan McKinley commented on SOLR-527:
I agree neither should approach should be committed
with:
https://issues.apache.org/jira/browse/SOLR-131
I clicked the I'm willing to mentor this student button, and we will
see what happens.
ryan
On Apr 3, 2008, at 6:17 PM, Matthias Epheser wrote:
Ryan McKinley schrieb:
Hey Matthias-
I just checked the pending Application list and don't
[
https://issues.apache.org/jira/browse/SOLR-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-525.
Resolution: Duplicate
Thanks for posting a solution! This is the same as SOLR-435, but that has
Hi Matthias-
Your demo looks great. I'd love to see a general solr javascript
library.
I need to look more at what it takes to be a mentor, but I'd be
willing to do that.
ryan
On Apr 1, 2008, at 9:31 AM, Matthias Epheser wrote:
Hello community
I am a student from Vienna currently
Grant Ingersoll wrote:
I'm looking a bit at the Multicore stuff and I am wondering why we are
deprecating code that hasn't been released? Shouldn't we just make it
right?
The deprecation is the outcome of an unresolved discussion ;) and yes,
it should be resolved.
The issue is how to make
Grant Ingersoll wrote:
More on multicore:
Would it also make sense for there to be a MultiCore(String dir, File
config) constructor that just calls load()?
In what context are you calling new MultiCore() directly? The
getInstance() bit is there so that if someone else modifies the
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-350:
---
Attachment: SOLR-350-RemoveStatic.patch
remove SolrMultiCore references from JSP
Manage Multiple
check the latest patch...
Grant Ingersoll wrote:
It seems like the MultiCore instance could be put into the Servlet
Context, then index.jsp would have access to it.
On Mar 25, 2008, at 9:32 AM, Ryan McKinley wrote:
Grant Ingersoll wrote:
More on multicore:
Would it also make sense
If it makes something easier, I think that is fine.
Grant Ingersoll wrote:
More on multicore:
Would it also make sense for there to be a MultiCore(String dir, File
config) constructor that just calls load()?
-Grant
What is exampleAnalysis?
http://svn.apache.org/repos/asf/lucene/solr/trunk/example/exampleAnalysis/
The tests all pass with it removed.
do we need it? It seems like it may make things more confusing... In
my view, one post.sh script is better then two.
ryan
[
https://issues.apache.org/jira/browse/SOLR-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-503.
Resolution: Fixed
restructure codebase to test .jsp files
Chris Hostetter wrote:
: and then removing the /src/webapp/resources directory?
i'm confused ... where would the JSPs go?
rather then
/src/webapp/resoures/admin/index.jsp
/src/webapp/admin/index.jsp
this way we could debug directly from /src/webapp/
: I imagine the reason to have
: Ok, then let me revise my proposal to:
: /src/webapp/java/(all java classes)
: /src/webapp/web/index.jsp
: /src/webapp/web/admin/...
: /src/webapp/web/WEB-INF/...
Yeah, got it ... I'm totally on board with that.
Without objection, I'll go ahead and do this. Patches with 'move' don't
McKinley
Assignee: Ryan McKinley
Priority: Minor
Fix For: 1.3
Change the package layout so we can test .jsp files from our embedded jetty
test.
check:
http://www.nabble.com/restructure-webapp-code-so-we-can-easily-test-.jsp-td15987151.html
--
This message
How do you feel about moving:
/src/webapp/src/org...
into
/src/java/org...
and then removing the /src/webapp/resources directory?
The reason for this change is:
1) more standard layout
2) The tests could easily run /admin/ and the .jsp files -- this would
avoid any problems like my most
[
https://issues.apache.org/jira/browse/SOLR-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12575857#action_12575857
]
Ryan McKinley commented on SOLR-498:
Hymmm, so you are trying to develop by putting your
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12574839#action_12574839
]
Ryan McKinley commented on SOLR-350:
Henri -- i just the previous patch. If you make
Any concrete projects we should consider?
-- Forwarded message --
From: Ross Gardler [EMAIL PROTECTED]
Date: Feb 29, 2008 5:34 PM
Subject: GSoC projects
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Google are running GSoC again this year.
Discussion of GSoC events happens on
[
https://issues.apache.org/jira/browse/SOLR-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-476.
Resolution: Fixed
Fix Version/s: 1.3
commited in rev 632228
CommonsHttpSolrServer should
[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-350:
---
Attachment: solr-350.patch
Updated patch for /trunk and fixed the dispatcher problem.
I think
[
https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572542#action_12572542
]
Ryan McKinley commented on SOLR-303:
{quote}Given that most of this is new functionality
(maybe a better question for solr-user... but)
which offsets are you talking about? The tokens? Are you looking for
something like analysis.jsp or SOLR-477?
Steve Suppe wrote:
Hello,
I'm looking into returning the offsets for various fields I've created
in a JSON object. Is there some
This is a possibility, but I was thinking if I
could get SOLR to return that information in the initial JSON, then I
could save a step and speed things up immensely.
nothing off the shelf to do it... you may want to look at implementing a
search component to augment the response with
[
https://issues.apache.org/jira/browse/SOLR-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-476:
---
Attachment: SOLR-476.patch
updated the patch so that it
1. sets the wt and version based
501 - 600 of 1482 matches
Mail list logo
