[
https://issues.apache.org/jira/browse/SOLR-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1592:
-
Attachment: SOLR-1592.patch
added a method to write cdata also
> Refactor XMLWriter startTag to allow arb
[
https://issues.apache.org/jira/browse/SOLR-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1592:
-
Attachment: SOLR-1592.patch
isn't this good enough?
> Refactor XMLWriter startTag to allow arbitrary attr
[
https://issues.apache.org/jira/browse/SOLR-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1587.
Resolution: Fixed
Fix Version/s: 1.5
committed.
> Propagating fl=*,score to shards
> ---
[
https://issues.apache.org/jira/browse/SOLR-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1587:
---
Attachment: SOLR-1587.patch
Attaching patch + test that treats "score" like "*,score" for distributed
[
https://issues.apache.org/jira/browse/SOLR-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1595.
Resolution: Fixed
Fix Version/s: 1.5
committed.
> StreamingUpdateSolrServer doesn't specifyi
[
https://issues.apache.org/jira/browse/SOLR-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781734#action_12781734
]
Yonik Seeley commented on SOLR-1595:
The included test fails (w/o the rest of the patch)
[
https://issues.apache.org/jira/browse/SOLR-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1595:
---
Attachment: SOLR-1595.patch
Here's the patch.
> StreamingUpdateSolrServer doesn't specifying UTF-8 wh
On Mon, Nov 23, 2009 at 7:04 PM, Chris Hostetter
wrote:
> XMLWriter was originally created
> to be a wrapper arround a java.io.Writer that had convinent heper methods
> for generating a specific XML response format (ie: wt=xml) back before
> Solr even supported multiple output types.
Indeed - my
Hey Hoss,
>
> : regular trunk structure at some point down the road. What's the SOLR
> : versioning scheme by the way? Is it:
>
> that's part of the problem (and the reason why comments about the "back
> compat" commitments for Solr have come up in this thread) ... Solr is a
> young enough proje
Hi Hoss,
Comments inline:
>
> : Potentially -- my problem is, why is XMLWriter a sacred cow? There's not
>
> I'm not trying to suggest that it should be ... my point wasn't to
> suggest that we shouldn't modify XMLWriter because it needs to be
> preserved as is -- my point was that given XMLWr
: Potentially -- my problem is, why is XMLWriter a sacred cow? There's not
I'm not trying to suggest that it should be ... my point wasn't to
suggest that we shouldn't modify XMLWriter because it needs to be
preserved as is -- my point was that given XMLWriter's origins, trying to
shoehorn gen
Hi Chris,
Thanks for the inputs: comments inline below:
>
> ...i think here may be a disconnect here between some of the goals you are
> describing and the purpose of XMLWriter. XMLWriter was originally created
> to be a wrapper arround a java.io.Writer that had convinent heper methods
> for ge
: Refactor XMLWriter startTag to allow arbitrary attributes to be written
...
: There are certain cases in which a user would like to write arbitrary
: attributes as part of the XML output for a field tag. Case in point: I'd
...i think here may be a disconnect here between some of the g
: What should the next version of Solr be?
personally, the way the question is phrased bothers me -- it feels like
the cart leading the horse.
I think the better questions to ask are...
Q1. should we actively try to upgrade to Lucene 3.x, or should we wait
for some demonstrated need/advanta
: regular trunk structure at some point down the road. What's the SOLR
: versioning scheme by the way? Is it:
that's part of the problem (and the reason why comments about the "back
compat" commitments for Solr have come up in this thread) ... Solr is a
young enough project that we've never mad
: Some functions could actually use it - say like ms().
: More could in the future if/when we type our value sources to avoid
: precision loss (i.e. sub(longfield1,longfield2) would work in long
: space, not float space).
my bad ... i tuned out the fact that both new variables had different
type
[
https://issues.apache.org/jira/browse/SOLR-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Au resolved SOLR-1594.
---
Resolution: Invalid
This same problem had been reported against and fixed in Tomcat. I have
reported it to t
On Mon, Nov 23, 2009 at 11:56 PM, Mark Miller wrote:
> Is that a proposal to never leave 1.x :) I guess numbers do allow it ...
>
> Lance Norskog wrote:
>> In practical terms, calling a release 2.0 means it will never finish.
>> "One last feature! No, really!" happens with 1.x. A Solr 2.0 will be
On Mon, Nov 23, 2009 at 5:36 PM, Chris Hostetter
wrote:
> : final long constant;
> : + final double dv;
> : + final float fv;
>
> ..can't the "final long constant" be removed completely now?
Some functions could actually use it - say like ms().
More could in the future if/when we type our va
Is that a proposal to never leave 1.x :) I guess numbers do allow it ...
Lance Norskog wrote:
> In practical terms, calling a release 2.0 means it will never finish.
> "One last feature! No, really!" happens with 1.x. A Solr 2.0 will be
> killed by "Let's rewrite this!"
>
> http://en.wikipedia.org
[
https://issues.apache.org/jira/browse/SOLR-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781688#action_12781688
]
Paul R. Brown commented on SOLR-1576:
-
I ended up dealing with this particular item by i
In practical terms, calling a release 2.0 means it will never finish.
"One last feature! No, really!" happens with 1.x. A Solr 2.0 will be
killed by "Let's rewrite this!"
http://en.wikipedia.org/wiki/Second-system_effect
On Mon, Nov 23, 2009 at 2:32 PM, Grant Ingersoll wrote:
>
> On Nov 19, 2009
[
https://issues.apache.org/jira/browse/SOLR-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781681#action_12781681
]
Hoss Man commented on SOLR-1576:
At the moment the response formatting is at the whim of the
Grant Ingersoll wrote:
On Nov 19, 2009, at 9:31 AM, Yonik Seeley wrote:
What should the next version of Solr be?
Options:
- have a Solr 2.0 with a lucene 3.x
+1. This gives us a chance to remove some deprecated stuff, too.
What would be the current development branch of Solr 2
:final long constant;
: + final double dv;
: + final float fv;
..can't the "final long constant" be removed completely now?
-Hoss
On Nov 19, 2009, at 9:31 AM, Yonik Seeley wrote:
> What should the next version of Solr be?
>
> Options:
>
> - have a Solr 2.0 with a lucene 3.x
+1. This gives us a chance to remove some deprecated stuff, too.
[
https://issues.apache.org/jira/browse/SOLR-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1596.
Resolution: Fixed
Fix Version/s: 1.5
Committed. Thanks to Chantal for the original bug repor
[
https://issues.apache.org/jira/browse/SOLR-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1596:
---
Attachment: SOLR-1596.patch
Patch attached:
- changes isClosed to a volatile
- overrides IndexWriter
rollback may be resulting ina SolrIndexWriter hat doesn't get closed properly
-
Key: SOLR-1596
URL: https://issues.apache.org/jira/browse/SOLR-1596
Project: Solr
Iss
On Mon, 9 Nov 2009, Chantal Ackermann wrote:
: > common pattern? ... do all of the people noticing these "POSSIBLE RESOURCE
: > LEAK" messages use rollback? is there any correlation between how much
: > you use rollback and how often you get one of these messages? (even if
: > they don't happen
[
https://issues.apache.org/jira/browse/SOLR-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781616#action_12781616
]
david commented on SOLR-1564:
-
I accidently left my signature, which includes my contact detail
[
https://issues.apache.org/jira/browse/SOLR-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781613#action_12781613
]
david commented on SOLR-1564:
-
Sorry, let me clarify:
- By deploying I meant adding the clas
[
https://issues.apache.org/jira/browse/SOLR-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781609#action_12781609
]
Hoss Man commented on SOLR-1595:
first noted here...
http://old.nabble.com/UTF-8-Character-S
StreamingUpdateSolrServer doesn't specifying UTF-8 when creating
OutputStreamWriter
---
Key: SOLR-1595
URL: https://issues.apache.org/jira/browse/SOLR-1595
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781568#action_12781568
]
Hoss Man commented on SOLR-1577:
I'm okay with it ... i'd like us to ultimately move to all
[
https://issues.apache.org/jira/browse/SOLR-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-1564.
Resolution: Invalid
> 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-tabpanel&focusedCommentId=12781563#action_12781563
]
Hoss Man commented on SOLR-1564:
I don't really understand what the issue is here.
PayloadT
[
https://issues.apache.org/jira/browse/SOLR-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781550#action_12781550
]
Yonik Seeley commented on SOLR-1577:
Yep. It does really seem hypothetical though - usi
[
https://issues.apache.org/jira/browse/SOLR-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781544#action_12781544
]
Hoss Man commented on SOLR-1577:
Doesn't this break things for (hypothetical) people who hav
[
https://issues.apache.org/jira/browse/SOLR-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-412:
--
Component/s: (was: search)
Response Writers
> XsltWriter does not output UTF-8 by default
>
[
https://issues.apache.org/jira/browse/SOLR-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-388:
--
Component/s: (was: search)
Response Writers
> Refactor ResponseWriters and Friends.
> --
[
https://issues.apache.org/jira/browse/SOLR-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-905:
--
Component/s: (was: search)
Response Writers
> wt type of json or ruby triggers error with le
: I'm trying to report some bugs/improvements, etc., while writing the
: GeoField stuff, and there aren't component classifications for JIRA
: issues: having to do with: schema, and the writer framework. These are
: major components that I think warrant a component in JIRA to classify
good p
[
https://issues.apache.org/jira/browse/SOLR-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781530#action_12781530
]
Hoss Man commented on SOLR-1594:
bq. So should we leave it up to the appserver to do the r
[
https://issues.apache.org/jira/browse/SOLR-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781522#action_12781522
]
Bill Au commented on SOLR-1594:
---
I just tried it and Jetty does double-escape:
org.apache.luc
[
https://issues.apache.org/jira/browse/SOLR-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1290#action_1290
]
Hoss Man edited comment on SOLR-1563 at 11/23/09 6:27 PM:
--
I've de
[
https://issues.apache.org/jira/browse/SOLR-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781513#action_12781513
]
Yonik Seeley commented on SOLR-1594:
Ahhh. If we escape it, will it then be double esca
[
https://issues.apache.org/jira/browse/SOLR-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781507#action_12781507
]
Bill Au commented on SOLR-1594:
---
Jetty is sanitizing both the HTTP response line and the respo
[
https://issues.apache.org/jira/browse/SOLR-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781504#action_12781504
]
Yonik Seeley commented on SOLR-1594:
OK
{code}
curl 'http://localhost:8983/solr/sele
[
https://issues.apache.org/jira/browse/SOLR-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781496#action_12781496
]
Bill Au commented on SOLR-1594:
---
Try running this query:
solr/select/?q=title:"alert("xss")
[
https://issues.apache.org/jira/browse/SOLR-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781491#action_12781491
]
Yonik Seeley commented on SOLR-1594:
What bad things happen w/o this patch?
> SolrDispa
[
https://issues.apache.org/jira/browse/SOLR-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781489#action_12781489
]
Grant Ingersoll commented on SOLR-1302:
---
Added strdist - string distance, too, which u
https://issues.apache.org/jira/browse/SOLR-1594
Bill
On Mon, Nov 23, 2009 at 11:45 AM, Bill Au wrote:
> I dug deeper and discovered that teh exception message is being added to
> the HTTP response line by SolrDIspatchFilter. So there is where the fix
> should be made. I will open a Jira and a
[
https://issues.apache.org/jira/browse/SOLR-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Au updated SOLR-1594:
--
Attachment: solr-1594.patch
> SolrDispatchFilter needs to sanitize exception message
> -
SolrDispatchFilter needs to sanitize exception message
--
Key: SOLR-1594
URL: https://issues.apache.org/jira/browse/SOLR-1594
Project: Solr
Issue Type: Bug
Affects Versions: 1.4
I dug deeper and discovered that teh exception message is being added to the
HTTP response line by SolrDIspatchFilter. So there is where the fix should
be made. I will open a Jira and attach a patch.
Bill
On Fri, Nov 20, 2009 at 5:34 PM, Bill Au wrote:
> I just noticed that the message of Luc
[
https://issues.apache.org/jira/browse/SOLR-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1580.
---
Resolution: Fixed
Thanks Lance!
> Solr Configuration ignores 'mergeFactor' parameter, always uses Luc
[
https://issues.apache.org/jira/browse/SOLR-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1593.
Resolution: Fixed
committed.
> reverse wildcard filter doesn't work for chars outside the BMP
> ---
[
https://issues.apache.org/jira/browse/SOLR-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781442#action_12781442
]
Robert Muir commented on SOLR-1593:
---
patch looks good to me.
i guess in the future if libs
[
https://issues.apache.org/jira/browse/SOLR-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1593:
---
Attachment: SOLR-1593.patch
Patch, with tests, using a slightly modified version of Robert's reverse m
reverse wildcard filter doesn't work for chars outside the BMP
--
Key: SOLR-1593
URL: https://issues.apache.org/jira/browse/SOLR-1593
Project: Solr
Issue Type: Bug
Affects Versi
[
https://issues.apache.org/jira/browse/SOLR-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1584.
Resolution: Fixed
committed.
> setIncludeScore is added to the "FL" field instead of being concated
[
https://issues.apache.org/jira/browse/SOLR-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1566:
-
Description:
Currently it is not possible for components to add fields to outgoing documents
which are no
[
https://issues.apache.org/jira/browse/SOLR-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1566:
-
Attachment: SOLR-1566.patch
untested patch. But
I am happy with the changes I have made. If others think
64 matches
Mail list logo
