[jira] Created: (SOLR-794) ClientUtils.escapeQueryChars escapes chars a bit aggressive
ClientUtils.escapeQueryChars escapes chars a bit aggressive --- Key: SOLR-794 URL: https://issues.apache.org/jira/browse/SOLR-794 Project: Solr Issue Type: Bug Components: clients - java Affects Versions: 1.3 Reporter: Koji Sekiguchi Priority: Trivial Fix For: 1.3.1, 1.4 This was talked before at: http://www.nabble.com/ClientUtils-escape-query-td18833559.html I didn't notice it at that time though. This method outputs weird string when Japanese letters are given for example. J1J2J3J4J5 = \J1\J2\J3\J4\J5 We don't want to see it. It should use QueryParser.escape() code as it says in javadoc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-794) ClientUtils.escapeQueryChars escapes chars a bit aggressive
[ https://issues.apache.org/jira/browse/SOLR-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Sekiguchi updated SOLR-794: Attachment: SOLR-794.patch The patch uses QueryParser.escape() code. ClientUtils.escapeQueryChars escapes chars a bit aggressive --- Key: SOLR-794 URL: https://issues.apache.org/jira/browse/SOLR-794 Project: Solr Issue Type: Bug Components: clients - java Affects Versions: 1.3 Reporter: Koji Sekiguchi Priority: Trivial Fix For: 1.3.1, 1.4 Attachments: SOLR-794.patch This was talked before at: http://www.nabble.com/ClientUtils-escape-query-td18833559.html I didn't notice it at that time though. This method outputs weird string when Japanese letters are given for example. J1J2J3J4J5 = \J1\J2\J3\J4\J5 We don't want to see it. It should use QueryParser.escape() code as it says in javadoc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Create new core by solrj API fails
Creating new Core By solrj API (CoreAdminRequest.createCore) fails because it doesn't set name parameter in getParameters method of CoreAdminRequest class solr version :1.3 Parisa -- View this message in context: http://www.nabble.com/Create-new-core-by-solrj-API-fails-tp19740822p19740822.html Sent from the Solr - Dev mailing list archive at Nabble.com.
[jira] Created: (SOLR-795) spellcheck: buildOnOptimize
spellcheck: buildOnOptimize
---
Key: SOLR-795
URL: https://issues.apache.org/jira/browse/SOLR-795
Project: Solr
Issue Type: New Feature
Components: spellchecker
Affects Versions: 1.3
Reporter: Jason Rennie
I see that there's an option to automatically rebuild the spelling index on a
commit. That's a nice feature that we'll consider using, but we run commits
every few thousand document updates, which would yield ~100 spelling index
rebuilds a day. OTOH, we run an optimize about once/day which seems like a
more appropriate schedule for rebuilding the spelling index.
Is there or could there be an option to rebuild the spelling index on optimize?
Grant:
Seems reasonable, could almost do it via the postOptimize call back already in
the config, except the SpellCheckComponent's EvenListener is private static and
has an empty postCommit implementation (which is what is called after
optimization, since it is just like a commit in many ways)
Thus, a patch would be needed.
Shalin:
postCommit/postOptimize callbacks happen after commit/optimize but before a
new searcher is opened. Therefore, it is not possible to re-build spellcheck
index on those events without opening a IndexReader directly on the solr
index. That is why the event listener in SpellCheckComponent uses the
newSearcher listener to build on commits.
I don't think there is anything in the API currently to do what Jason wants.
Hoss:
FWIW: I believe it has to work that way because postCommit events might
modify the index. (but i'm just guessing)
couldn't the Listener's newSearcher() method just do something like
this...
if (rebuildOnlyAfterOptimize
! (newSearcher.getReader().isOptimized()
! oldSearcher.getReader().isOptimized()) {
return;
} else {
// current impl
}
...assuming a new rebuildOnlyAfterOptimize option was added?
Grant:
That seems reasonable.
Another thing to think about, is maybe it is useful to provide some event
metadata to the events that contain information about what triggered them.
Something like a SolrEvent class such that postCommit looks like
postCommit(SolrEvent evt)
and
public void newSearcher(SolrEvent evt, SolrIndexSearcher newSearcher,
SolrIndexSearcher currentSearcher);
Of course, since SolrEventListener is an interface...
Shalin:
Yup, that will work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-680) StatsComponent - get min, max, sum, qt, avg of number fields
[
https://issues.apache.org/jira/browse/SOLR-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12635758#action_12635758
]
Ryan McKinley commented on SOLR-680:
good catch -- that would even work in distributed mode!
However, median still requires a second pass. (unless you assume there are no
null values)
If we do a second pass, we could also calculate Q1 and Q3 (1st and 3rd quarter
deviation) -- JFreeChart has a nice program to graph that :)
StatsComponent - get min, max, sum, qt, avg of number fields
Key: SOLR-680
URL: https://issues.apache.org/jira/browse/SOLR-680
Project: Solr
Issue Type: New Feature
Components: search
Reporter: Koji Sekiguchi
Priority: Minor
Fix For: 1.4
Attachments: SOLR-680.patch, SOLR-680.patch, SOLR-680.patch,
SOLR-680.patch
StatsComponent - it returns min,max,sum,qt,avg of specified number fields:
request parameters:
stats=onstats.field=price
{code:xml}
stats
stats_fields
lst name=price
double name=min10/double
double name=max30/double
double name=avg20/double
double name=sum60/double
double name=qt3/double
/lst
/stats_fields
/stats
{code}
WRT stats, the component can output sum and avg, but not sd and var.
USE CASE:
StatsComponent can be used to get market price of DocSet e.g. rental
housing site, package tour site.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-680) StatsComponent - get min, max, sum, qt, avg of number fields
[
https://issues.apache.org/jira/browse/SOLR-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-680:
---
Attachment: SOLR-680.patch
updated:
* calculate stddev in first pass -- and works distributed (thanks Sean!)
* throws a full error when asking for a bad field -- this seems better then
catching it and adding it to the response.
* changed param stddev to twopass -- now it is a flag to calculate things
that require a 2nd pass through the data. Currently only median
I'd like to commit this soon...
StatsComponent - get min, max, sum, qt, avg of number fields
Key: SOLR-680
URL: https://issues.apache.org/jira/browse/SOLR-680
Project: Solr
Issue Type: New Feature
Components: search
Reporter: Koji Sekiguchi
Priority: Minor
Fix For: 1.4
Attachments: SOLR-680.patch, SOLR-680.patch, SOLR-680.patch,
SOLR-680.patch, SOLR-680.patch
StatsComponent - it returns min,max,sum,qt,avg of specified number fields:
request parameters:
stats=onstats.field=price
{code:xml}
stats
stats_fields
lst name=price
double name=min10/double
double name=max30/double
double name=avg20/double
double name=sum60/double
double name=qt3/double
/lst
/stats_fields
/stats
{code}
WRT stats, the component can output sum and avg, but not sd and var.
USE CASE:
StatsComponent can be used to get market price of DocSet e.g. rental
housing site, package tour site.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-680) StatsComponent - get min, max, sum, qt, avg of number fields
[
https://issues.apache.org/jira/browse/SOLR-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12635779#action_12635779
]
Koji Sekiguchi commented on SOLR-680:
-
Lars, Ryan and Sean -- thank you for your comments and contribution on this!
And thanks again Ryan for Wiki document :)
http://wiki.apache.org/solr/StatsComponent
I was thinking whether I could implement arbitrary function other than sum(),
avg(),... just after I opened this ticket, as Yonik mentioned in this thread:
http://www.nabble.com/Sum-of-one-field-td18815666.html#a18854371, but soon I
couldn't find time to think about it and was apart from this. I'd like to see
updated patch when I am available, hopefully soon. :)
StatsComponent - get min, max, sum, qt, avg of number fields
Key: SOLR-680
URL: https://issues.apache.org/jira/browse/SOLR-680
Project: Solr
Issue Type: New Feature
Components: search
Reporter: Koji Sekiguchi
Priority: Minor
Fix For: 1.4
Attachments: SOLR-680.patch, SOLR-680.patch, SOLR-680.patch,
SOLR-680.patch, SOLR-680.patch
StatsComponent - it returns min,max,sum,qt,avg of specified number fields:
request parameters:
stats=onstats.field=price
{code:xml}
stats
stats_fields
lst name=price
double name=min10/double
double name=max30/double
double name=avg20/double
double name=sum60/double
double name=qt3/double
/lst
/stats_fields
/stats
{code}
WRT stats, the component can output sum and avg, but not sd and var.
USE CASE:
StatsComponent can be used to get market price of DocSet e.g. rental
housing site, package tour site.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (SOLR-680) StatsComponent - get min, max, sum, qt, avg of number fields
[
https://issues.apache.org/jira/browse/SOLR-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12635779#action_12635779
]
koji edited comment on SOLR-680 at 9/30/08 9:32 AM:
--
Lars, Ryan and Sean -- thank you for your comments and contribution on this!
And thanks again Ryan for Wiki document :)
http://wiki.apache.org/solr/StatsComponent
I was thinking whether I could implement arbitrary function other than sum(),
avg(),... just after I opened this ticket, as Yonik mentioned in this thread:
http://www.nabble.com/Sum-of-one-field-td18815666.html#a18854371, but soon I
couldn't find time to think about it and was apart from this. I'd like to see
your updated patch when I am available, hopefully soon. :)
was (Author: koji):
Lars, Ryan and Sean -- thank you for your comments and contribution on this!
And thanks again Ryan for Wiki document :)
http://wiki.apache.org/solr/StatsComponent
I was thinking whether I could implement arbitrary function other than sum(),
avg(),... just after I opened this ticket, as Yonik mentioned in this thread:
http://www.nabble.com/Sum-of-one-field-td18815666.html#a18854371, but soon I
couldn't find time to think about it and was apart from this. I'd like to see
updated patch when I am available, hopefully soon. :)
StatsComponent - get min, max, sum, qt, avg of number fields
Key: SOLR-680
URL: https://issues.apache.org/jira/browse/SOLR-680
Project: Solr
Issue Type: New Feature
Components: search
Reporter: Koji Sekiguchi
Priority: Minor
Fix For: 1.4
Attachments: SOLR-680.patch, SOLR-680.patch, SOLR-680.patch,
SOLR-680.patch, SOLR-680.patch
StatsComponent - it returns min,max,sum,qt,avg of specified number fields:
request parameters:
stats=onstats.field=price
{code:xml}
stats
stats_fields
lst name=price
double name=min10/double
double name=max30/double
double name=avg20/double
double name=sum60/double
double name=qt3/double
/lst
/stats_fields
/stats
{code}
WRT stats, the component can output sum and avg, but not sd and var.
USE CASE:
StatsComponent can be used to get market price of DocSet e.g. rental
housing site, package tour site.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
LogoContest Process Timeline ... was: Re: [Solr Wiki] Update of LogoContest by HossMan
: Ok, based on what little feedback I've gotten from the PRC this is about : as good as I can come up with at this point. What do people think of this : as it is? what do people think of the timeline? : : http://wiki.apache.org/solr/LogoContest Hmmm... no feedback in the last 3 days. Not sure what to make of that. My own thought process the last few days has ben that the deadline as listed (October 28th, 2008) is too rushed ... particularly considering none of the Logo's currently submitted meet the criteria required by the PRC (that it contain the word Apache). It would be nice to unveil the new logo at ApacheCon -- but it would also be nice to use ApacheCon to drum up buzz about the contest and encourage more submissions. thoughts? -Hoss
[jira] Commented: (SOLR-791) Allow to submit config and schema when creating a new core
[
https://issues.apache.org/jira/browse/SOLR-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12635803#action_12635803
]
Hoss Man commented on SOLR-791:
---
This doesn't seem like something that should be a built in feature of Solr ...
userswho want to be able to remotely install config files should use WebDAV or
other tools designed for such a purpose.
Allow to submit config and schema when creating a new core
--
Key: SOLR-791
URL: https://issues.apache.org/jira/browse/SOLR-791
Project: Solr
Issue Type: New Feature
Components: clients - java
Affects Versions: 1.3
Reporter: Gunnar Wagenknecht
Currently it's possible to create cores remotely via SolrJ.
{code}
CoreAdminRequest.createCore(acore, acoreinstancedir, adminServer);
{code}
However, this process is incomplete because I need to manually log onto the
remote server and place a configuration file as well as a schema file into
the {{conf/}} folder in the {{acoreinstancedir/}}. It would be great it I can
simply submit those files together with the create core request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (SOLR-746) Make it possible to omit responseheader
: how about removing the header right before calling the : QueryResponseWriter.write() ? so that wed do not have to do the check : in many different places : : We can add one line into SolrDispatchFilter and it should be fine . if we want to do it as a core param (akin to qt, wt, echoHandler, echoParams) then the simlest thing to do is have SolrCore skip the call to setResponseHeaderValues ... i was just pointing out that moving that call into RequestHandlers isn't back compatible, and it would be possible to solve this in the response writers if we felt like it really only made sense in certain situations. But i'm fine with it being a core param as well since hte core is what currently computes this stuff. : : On Sun, Sep 28, 2008 at 7:41 AM, Hoss Man (JIRA) [EMAIL PROTECTED] wrote: : : [ https://issues.apache.org/jira/browse/SOLR-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12635201#action_12635201 ] : : Hoss Man commented on SOLR-746: : --- : : that wouldn't be back compatible for existing users who have written their own handlers. : : the simplest approach would probably be leave SolrCore alone and just modify the ResponseWriters where we think this would be relevant (json and XML i'm guessing) to not bother outputting the responseHeader if a certain param is set. : : (the time spent in setResponseHeaderValues should be negligable) : : Make it possible to omit responseheader : --- : : Key: SOLR-746 : URL: https://issues.apache.org/jira/browse/SOLR-746 : Project: Solr : Issue Type: Improvement : Components: search : Affects Versions: 1.3 : Reporter: Noble Paul : Fix For: 1.4 : : : In a lot of cases we do not actually need the data included in the : header.So we just waste bandwidth, processing to write and read this . : And there are requests where the responses are quite small and too frequent (say for auto-suggest feature) where this overhead is unnecessary : we should add a request parameter omitHeader=true|false . Default : should be false . If it is true let us not send the header itself : http://markmail.org/message/rcobnn4g2qyzygmp : : -- : This message is automatically generated by JIRA. : - : You can reply to this email to add a comment to the issue online. : : : : : : -- : --Noble Paul : -Hoss
Re: LogoContest Process Timeline ... was: Re: [Solr Wiki] Update of LogoContest by HossMan
Hi, May I have a question? What is PRC? (And I am sorry for not delivering other Logo proposals ... it is due to [blahblahblah]*) []* substitute traditional lamer talk Lukas On Tue, Sep 30, 2008 at 8:22 PM, Chris Hostetter [EMAIL PROTECTED]wrote: : Ok, based on what little feedback I've gotten from the PRC this is about : as good as I can come up with at this point. What do people think of this : as it is? what do people think of the timeline? : : http://wiki.apache.org/solr/LogoContest Hmmm... no feedback in the last 3 days. Not sure what to make of that. My own thought process the last few days has ben that the deadline as listed (October 28th, 2008) is too rushed ... particularly considering none of the Logo's currently submitted meet the criteria required by the PRC (that it contain the word Apache). It would be nice to unveil the new logo at ApacheCon -- but it would also be nice to use ApacheCon to drum up buzz about the contest and encourage more submissions. thoughts? -Hoss -- http://blog.lukas-vlcek.com/
[jira] Resolved: (SOLR-588) Statistical info in facet fields
[ https://issues.apache.org/jira/browse/SOLR-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar resolved SOLR-588. Resolution: Duplicate Functionality is being actively worked on in SOLR-680 Statistical info in facet fields Key: SOLR-588 URL: https://issues.apache.org/jira/browse/SOLR-588 Project: Solr Issue Type: New Feature Components: search Affects Versions: 1.1.0, 1.2, 1.3 Reporter: Jonathan Leibiusky Priority: Minor Fix For: 1.4 Attachments: statisticalfacet.patch This patch will add statistical information to the facet. When adding facet.statistical=true, solr will add max and min value and if it's a numeric field, it will add SD, CV and MEAN. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: LogoContest Process Timeline ... was: Re: [Solr Wiki] Update of LogoContest by HossMan
: May I have a question? What is PRC? Sorry: it's the Public Relations Comittee. They don't have much of a web presence, so i can't include a handy URL explaining all about them, but they are the committee established by the ASF Board to oversee all things related to Apache PR (including branding and the policies for projects Logos [rant]which projects are expected to follow, but aren't posted anywhere for people to find[/rant].) http://www.apache.org/foundation/how-it-works.html#other : (And I am sorry for not delivering other Logo proposals ... it is due to no problem, we're all just voluneering on this afterall -- the question is do you (as a graphic artist) think 4 weeks is enough time to see some really good, creative designs come in? -Hoss
Re: LogoContest Process Timeline ... was: Re: [Solr Wiki] Update of LogoContest by HossMan
On Tue, Sep 30, 2008 at 9:12 PM, Chris Hostetter [EMAIL PROTECTED]wrote: : May I have a question? What is PRC? Sorry: it's the Public Relations Comittee. They don't have much of a web presence, so i can't include a handy URL explaining all about them, but they are the committee established by the ASF Board to oversee all things related to Apache PR (including branding and the policies for projects Logos [rant]which projects are expected to follow, but aren't posted anywhere for people to find[/rant].) http://www.apache.org/foundation/how-it-works.html#other OK, what PRC has to do with the log design? Is there any particular constraint/request that the logo design must follow? What is it? You mentioned that the logo design has to contain a word Apache, are there any other requirements like this? : (And I am sorry for not delivering other Logo proposals ... it is due to no problem, we're all just voluneering on this afterall -- the question is do you (as a graphic artist) think 4 weeks is enough time to see some really good, creative designs come in? -Hoss 4 weeks sounds good. I will deliver more stuff by the end of this week. (Wow! did I say this publicly?) Lukas
[jira] Commented: (SOLR-791) Allow to submit config and schema when creating a new core
[
https://issues.apache.org/jira/browse/SOLR-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12635825#action_12635825
]
Gunnar Wagenknecht commented on SOLR-791:
-
Hmm, but why is it possible to setup cores remotely? It sounds unreasonable to
install, setup and maintain a separate systemto allow WebDAV just for uploading
configuration files.
It would be easier if I can make a single POSTrequest to setup create a new
core. This would be a single, atomic request and avoids a second system which
helps keeping the operational costs under control.
Allow to submit config and schema when creating a new core
--
Key: SOLR-791
URL: https://issues.apache.org/jira/browse/SOLR-791
Project: Solr
Issue Type: New Feature
Components: clients - java
Affects Versions: 1.3
Reporter: Gunnar Wagenknecht
Currently it's possible to create cores remotely via SolrJ.
{code}
CoreAdminRequest.createCore(acore, acoreinstancedir, adminServer);
{code}
However, this process is incomplete because I need to manually log onto the
remote server and place a configuration file as well as a schema file into
the {{conf/}} folder in the {{acoreinstancedir/}}. It would be great it I can
simply submit those files together with the create core request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
