[jira] Updated: (SOLR-1600) A single value in amultivalued field means the value will not be a collection for javabin

[ https://issues.apache.org/jira/browse/SOLR-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-1600: - Attachment: SOLR-1600.patch A single value in amultivalued field means the value will not be a

[jira] Resolved: (SOLR-1600) A single value in amultivalued field means the value will not be a collection for javabin

[ https://issues.apache.org/jira/browse/SOLR-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-1600. -- Resolution: Fixed commited r884032 A single value in amultivalued field means the value will not be

[jira] Resolved: (SOLR-1516) DocumentList and Document QueryResponseWriter

[ https://issues.apache.org/jira/browse/SOLR-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-1516. -- Resolution: Fixed committed r884037 Thanks Mattman. removed author tags because Lucene has a policy

[jira] Updated: (SOLR-1489) A UTF-8 character is output twice (Bug in Jetty)

[ https://issues.apache.org/jira/browse/SOLR-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Sekiguchi updated SOLR-1489: - Attachment: SOLR-1489.patch Attached patch fixes the above failure, but I got another failure (no

[jira] Commented: (SOLR-1599) Improve IDF and relevance by separately indexing different entity types sharing a common schema

[ https://issues.apache.org/jira/browse/SOLR-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782388#action_12782388 ] Graham Poulter commented on SOLR-1599: -- This is what could happen when indexing

[jira] Issue Comment Edited: (SOLR-1599) Improve IDF and relevance by separately indexing different entity types sharing a common schema

[ https://issues.apache.org/jira/browse/SOLR-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782388#action_12782388 ] Graham Poulter edited comment on SOLR-1599 at 11/25/09 12:28 PM:

[jira] Updated: (SOLR-1601) Schema browser does not indicate presence of charFilter

[ https://issues.apache.org/jira/browse/SOLR-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Sekiguchi updated SOLR-1601: - Component/s: Schema and Analysis Affects Version/s: 1.4 Fix Version/s: 1.5

[jira] Updated: (SOLR-1601) Schema browser does not indicate presence of charFilter

[ https://issues.apache.org/jira/browse/SOLR-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Sekiguchi updated SOLR-1601: - Attachment: SOLR-1601.patch Will commit shortly. Schema browser does not indicate presence of

[jira] Commented: (SOLR-1516) DocumentList and Document QueryResponseWriter

[ https://issues.apache.org/jira/browse/SOLR-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782489#action_12782489 ] Chris A. Mattmann commented on SOLR-1516: - Thanks, Noble! DocumentList and

[jira] Resolved: (SOLR-1601) Schema browser does not indicate presence of charFilter

[ https://issues.apache.org/jira/browse/SOLR-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Sekiguchi resolved SOLR-1601. -- Resolution: Fixed Committed revision 884180. Thanks, Jake. Schema browser does not indicate

Re: Indexing multiple documents in Solr/SolrCell

: Question: : Can you index both metadata and content for multiple documents iteratively : in Solr? As i understand it, there is some ongoing work with the DataImportHandler so support this type of thing -- having entities from one DataSource refrnece other entities that are then processed

[jira] Created: (SOLR-1602) Refactor SOLR package structure to include o.a.solr.response and move QueryResponseWriters in there

Refactor SOLR package structure to include o.a.solr.response and move QueryResponseWriters in there --- Key: SOLR-1602 URL:

Re: [jira] Created: (SOLR-1592) Refactor XMLWriter startTag to allow arbitrary attributes to be written

: Sure, but my point was, I am still able to call xmlWriter.writePrim which : lets me write XML tags with unbound names in an arbitrary fashion. In other : words, I can make my field (for XML) instead of spitting out: Oh man ... WTF is writePrim doing marked public ?!?!?!?! ...this is why

Re: Solr 1.5 or 2.0?

: 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. : : Agreed, but now that the elephant has been identified in the

Re: Solr 1.5 or 2.0?

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. : :

Re: Solr 1.5 or 2.0?

: What would a 1.9 release mean in solr? : : Dooh -- after hitting send, i realized it would just mean: : Whatever we would do for the next release, but say 'after this, old APIs won't : be supported' but even that is still a vague statement: are we talking about the internal/plugin Java

[jira] Created: (SOLR-1603) Perl Response Writer

Perl Response Writer Key: SOLR-1603 URL: https://issues.apache.org/jira/browse/SOLR-1603 Project: Solr Issue Type: New Feature Components: Response Writers Reporter: Claudio Valente I've made a

[jira] Updated: (SOLR-1603) Perl Response Writer

[ https://issues.apache.org/jira/browse/SOLR-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudio Valente updated SOLR-1603: -- Attachment: SOLR-1603.patch Perl Response Writer Key:

Re: Solr 1.5 or 2.0?

Hi Guys, The process should be as formal as the community dictates, but I can't help but make the observation that increments in version numbers that are strange to those with some knowledge of artifact versioning will only be stranger to those without (i.e., adopters/users of SOLR). To me,

[jira] Assigned: (SOLR-1570) Complain loudly if uniqueKey field is definied but not stored=true,multiValued=false

[ https://issues.apache.org/jira/browse/SOLR-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar reassigned SOLR-1570: --- Assignee: Shalin Shekhar Mangar Complain loudly if uniqueKey field is

[jira] Commented: (SOLR-1570) Complain loudly if uniqueKey field is definied but not stored=true,multiValued=false

[ https://issues.apache.org/jira/browse/SOLR-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782599#action_12782599 ] Shalin Shekhar Mangar commented on SOLR-1570: - bq. And FWIW: even if Lance has a

[jira] Commented: (SOLR-1603) Perl Response Writer

[ https://issues.apache.org/jira/browse/SOLR-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782605#action_12782605 ] Simon Rosenthal commented on SOLR-1603: --- I'd be curious to know what the use case is

[jira] Resolved: (SOLR-1570) Complain loudly if uniqueKey field is definied but not stored=true,multiValued=false

[ https://issues.apache.org/jira/browse/SOLR-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar resolved SOLR-1570. - Resolution: Fixed Fix Version/s: 1.5 Committed revision 884263. Thanks!

Re: Solr 1.5 or 2.0?

On Nov 25, 2009, at 3:09 PM, Chris Hostetter wrote: : What would a 1.9 release mean in solr? : : Dooh -- after hitting send, i realized it would just mean: : Whatever we would do for the next release, but say 'after this, old APIs won't : be supported' but even that is still a vague

[jira] Commented: (SOLR-1564) payload plugin does not load on standard solr 1.4.0 distribution

[ https://issues.apache.org/jira/browse/SOLR-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782631#action_12782631 ] Joe Schaefer commented on SOLR-1564: I deleted your comment. Please readd the relevant

[jira] Updated: (SOLR-1564) payload plugin does not load on standard solr 1.4.0 distribution

[ https://issues.apache.org/jira/browse/SOLR-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Schaefer updated SOLR-1564: --- Comment: was deleted (was: Sorry, let me clarify: - By deploying I meant adding the class to an

[jira] Updated: (SOLR-1602) Refactor SOLR package structure to include o.a.solr.response and move QueryResponseWriters in there

[ https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated SOLR-1602: Attachment: SOLR-1602.Mattmann.112509.patch.txt * moves all writers from o.a.solr.request

[jira] Commented: (SOLR-1602) Refactor SOLR package structure to include o.a.solr.response and move QueryResponseWriters in there

[ https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782648#action_12782648 ] Chris A. Mattmann commented on SOLR-1602: - This patch also: * creates an

[jira] Commented: (SOLR-1603) Perl Response Writer

[ https://issues.apache.org/jira/browse/SOLR-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782694#action_12782694 ] Claudio Valente commented on SOLR-1603: --- I guess the use case is analogous to the use

[jira] Commented: (SOLR-412) XsltWriter does not output UTF-8 by default

[ https://issues.apache.org/jira/browse/SOLR-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782701#action_12782701 ] Hoss Man commented on SOLR-412: --- Ok, i've become comvinced that we should do something like the

Re: SOLR-1131 - Multiple Fields per Field Type

I'm having a hard time wrapping my head arround this entire concept ... i know part of my problem is that your example use case seems somewhat nonsensical... : As a simple proof of concept, imagine that I define a new FieldType : called PlusMinusIntFieldType that extends IntField. This

TestContentStreamDataSource failing on trunk

the lucene zone machine is down (see INFRA-2351) so i don't think nightly builds are running. On my local box i'm seeing TestContentStreamDataSource fail... junit.framework.AssertionFailedError: expected:Hello C1 but was:[Hello C1] at

[jira] Resolved: (SOLR-1558) QueryElevationComponent should fail to init if uniqueKey field isn't string

[ https://issues.apache.org/jira/browse/SOLR-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man resolved SOLR-1558. Resolution: Fixed Assignee: Hoss Man Committed revision 884393. Note that the code change only

[jira] Created: (SOLR-1605) ExtractingRequestHandler does not embed original document

ExtractingRequestHandler does not embed original document - Key: SOLR-1605 URL: https://issues.apache.org/jira/browse/SOLR-1605 Project: Solr Issue Type: Wish Components:

[jira] Commented: (SOLR-678) HTMLStripStandardTokenizerFactory doesn't interpret word boundaries on html tags correctly.

[ https://issues.apache.org/jira/browse/SOLR-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782741#action_12782741 ] Lance Norskog commented on SOLR-678: HTMLStripStandardTokenizerFactory Whitespace are

Re: TestContentStreamDataSource failing on trunk

SOLR-1600 ensures that for all mutivalued fields ,the response type is a collection.So your change is right On Thu, Nov 26, 2009 at 8:38 AM, Chris Hostetter hossman_luc...@fucit.org wrote: the lucene zone machine is down (see INFRA-2351) so i don't think nightly builds are running. On my

[jira] Updated: (SOLR-1602) Refactor SOLR package structure to include o.a.solr.response and move QueryResponseWriters in there

[ https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated SOLR-1602: Attachment: SOLR-1602.Mattmann.112509_02.patch.txt * newest patch includes updates to all

Re: [jira] Created: (SOLR-1592) Refactor XMLWriter startTag to allow arbitrary attributes to be written

Why don't we make the response writers deal w/ SolrDocument instead of lucene Document? That way we can get rid of a lot of ugly code. SOLR-1516 enables responsewriters to do that On Tue, Nov 24, 2009 at 6:44 AM, Yonik Seeley yo...@lucidimagination.com wrote: On Mon, Nov 23, 2009 at 7:04 PM,

[jira] Commented: (SOLR-1592) Refactor XMLWriter startTag to allow arbitrary attributes to be written

[ https://issues.apache.org/jira/browse/SOLR-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782767#action_12782767 ] Chris A. Mattmann commented on SOLR-1592: - Hey Noble: I like your latest patch. My

[jira] Commented: (SOLR-1592) Refactor XMLWriter startTag to allow arbitrary attributes to be written

[ https://issues.apache.org/jira/browse/SOLR-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782769#action_12782769 ] Noble Paul commented on SOLR-1592: -- committed r884411 Thanks Mattman Refactor XMLWriter

[jira] Commented: (SOLR-1592) Refactor XMLWriter startTag to allow arbitrary attributes to be written

[ https://issues.apache.org/jira/browse/SOLR-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782773#action_12782773 ] Chris A. Mattmann commented on SOLR-1592: - Thanks, Noble! This works for me. +1 to

[jira] Updated: (SOLR-1586) Create Spatial Point FieldTypes

[ https://issues.apache.org/jira/browse/SOLR-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated SOLR-1586: Attachment: SOLR-1586.Mattmann.112509.geopointandgeohash.patch.txt - updated patch based on

[jira] Resolved: (SOLR-1592) Refactor XMLWriter startTag to allow arbitrary attributes to be written

[ https://issues.apache.org/jira/browse/SOLR-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-1592. -- Resolution: Fixed Refactor XMLWriter startTag to allow arbitrary attributes to be written

[jira] Assigned: (SOLR-1592) Refactor XMLWriter startTag to allow arbitrary attributes to be written

[ https://issues.apache.org/jira/browse/SOLR-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul reassigned SOLR-1592: Assignee: Noble Paul Refactor XMLWriter startTag to allow arbitrary attributes to be written

[jira] Updated: (SOLR-1516) DocumentList and Document QueryResponseWriter

[ https://issues.apache.org/jira/browse/SOLR-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-1516: - Attachment: SOLR-1516.patch some API changes DocumentList and Document QueryResponseWriter

[jira] Commented: (SOLR-1516) DocumentList and Document QueryResponseWriter

[ https://issues.apache.org/jira/browse/SOLR-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782783#action_12782783 ] Noble Paul commented on SOLR-1516: -- it was not possible to write multiple DocList