[jira] Commented: (SOLR-939) ValueSourceRangeFilter/Query
[ https://issues.apache.org/jira/browse/SOLR-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679236#action_12679236 ] Yonik Seeley commented on SOLR-939: --- Right - it made sense to me to go through the FunctionQuery/ValueSource abstraction to do range filters, as it's a superset of just going off of the FieldCache (it could work with functions, FileFloatSource, and future payload or column-stored fields too). I've been meaning to get back to this patch... at a minimum it would need support for all of the field types as well as tests. I think I may even have some local updates since this last patch - I'll have to check. It would be nice if one could tag a field with info to use ValueSourceRangeFilter for any range queries... but it doesn't seem necessary before committing this underlying functionality. > ValueSourceRangeFilter/Query > > > Key: SOLR-939 > URL: https://issues.apache.org/jira/browse/SOLR-939 > Project: Solr > Issue Type: New Feature >Reporter: Yonik Seeley >Assignee: Yonik Seeley > Fix For: 1.4 > > Attachments: SOLR-939.patch > > > Ability to do a range query based on a FieldCache entry or a FunctionQuery > (ValueSource). > Equivalent to Lucene's FieldCacheRangeQuery -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-1046) nested queries in function query
nested queries in function query Key: SOLR-1046 URL: https://issues.apache.org/jira/browse/SOLR-1046 Project: Solr Issue Type: Bug Reporter: Yonik Seeley Fix For: 1.4 Allow nested queries (sub-queries of different types) from function query syntax -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-1046) nested queries in function query
[
https://issues.apache.org/jira/browse/SOLR-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1046:
---
Attachment: SOLR-1046.patch
The code for this was in Solr for some time - I just never got around to fixing
the bugs, testing and documenting it. Patch attached.
Examples:
// relevancy score of the sub-query specified by the qq var (lucene query by
default)
q=query($qq)&qq=+foo +bar baz
// value of the query specified by the qq argument (a dismax query) with a
default value of 1.0 for documents that don't match that query.
q=query($qq,1)&qq={!dismax qf=myfield pf=myfield}foo bar
// relevancy score of the lucene query with a default value of 0.1 for any
non-matching documents
query({!lucene v='body:apple +tag:[* TO *]'},0.1)
> nested queries in function query
>
>
> Key: SOLR-1046
> URL: https://issues.apache.org/jira/browse/SOLR-1046
> Project: Solr
> Issue Type: Bug
>Reporter: Yonik Seeley
> Fix For: 1.4
>
> Attachments: SOLR-1046.patch
>
>
> Allow nested queries (sub-queries of different types) from function query
> syntax
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-939) ValueSourceRangeFilter/Query
[
https://issues.apache.org/jira/browse/SOLR-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679282#action_12679282
]
Shalin Shekhar Mangar commented on SOLR-939:
bq. Right - it made sense to me to go through the FunctionQuery/ValueSource
abstraction to do range filters, as it's a superset of just going off of the
FieldCache (it could work with functions, FileFloatSource, and future payload
or column-stored fields too).
Very cool!
bq. It would be nice if one could tag a field with info to use
ValueSourceRangeFilter for any range queries
As an extra attribute in the schema? e.g.
{code:xml}
{code}
+1 for this. It is easier/cleaner than the local param syntax but I guess we'd
need to support both anyway. Solrj does not have API methods to manipulate
local params and I think this is a good time to add that support.
bq. I've been meaning to get back to this patch... at a minimum it would need
support for all of the field types as well as tests. I think I may even have
some local updates since this last patch - I'll have to check.
Can you post your updates? SOLR-940 (Trie support) is mostly done and I can try
to spend some time on this one. Per the 1.4 release discussion, these two are
the major features stopping the 1.4 release, though I'm sure we'll find more :)
> ValueSourceRangeFilter/Query
>
>
> Key: SOLR-939
> URL: https://issues.apache.org/jira/browse/SOLR-939
> Project: Solr
> Issue Type: New Feature
>Reporter: Yonik Seeley
>Assignee: Yonik Seeley
> Fix For: 1.4
>
> Attachments: SOLR-939.patch
>
>
> Ability to do a range query based on a FieldCache entry or a FunctionQuery
> (ValueSource).
> Equivalent to Lucene's FieldCacheRangeQuery
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-1046) nested queries in function query
[ https://issues.apache.org/jira/browse/SOLR-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley resolved SOLR-1046. Resolution: Fixed committed. I'll work on updating the Wiki shortly. > nested queries in function query > > > Key: SOLR-1046 > URL: https://issues.apache.org/jira/browse/SOLR-1046 > Project: Solr > Issue Type: Bug >Reporter: Yonik Seeley > Fix For: 1.4 > > Attachments: SOLR-1046.patch > > > Allow nested queries (sub-queries of different types) from function query > syntax -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-1047) support for facet method
support for facet method Key: SOLR-1047 URL: https://issues.apache.org/jira/browse/SOLR-1047 Project: Solr Issue Type: Improvement Components: clients - ruby - flare Affects Versions: 1.3 Reporter: ian connor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1047) support for facet method
[ https://issues.apache.org/jira/browse/SOLR-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679368#action_12679368 ] ian connor commented on SOLR-1047: -- *** standard.rb 2009-03-05 16:29:51.0 -0500 --- new.standard.rb 2009-03-05 16:31:24.0 -0500 *** *** 75,80 --- 75,81 hash["facet.mincount"] = @params[:facets][:mincount] hash["facet.prefix"] = @params[:facets][:prefix] hash["facet.offset"] = @params[:facets][:offset] + hash["facet.method"] = @params[:facets][:method] if @params[:facets][:method] if @params[:facets][:fields] # facet fields are optional (could be facet.query only) @params[:facets][:fields].each do |f| if f.kind_of? Hash > support for facet method > > > Key: SOLR-1047 > URL: https://issues.apache.org/jira/browse/SOLR-1047 > Project: Solr > Issue Type: Improvement > Components: clients - ruby - flare >Affects Versions: 1.3 >Reporter: ian connor > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-1047) support for facet method
[ https://issues.apache.org/jira/browse/SOLR-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Hatcher resolved SOLR-1047. Resolution: Fixed committed and v0.0.7 gem uploaded to rubyforge. thanks! > support for facet method > > > Key: SOLR-1047 > URL: https://issues.apache.org/jira/browse/SOLR-1047 > Project: Solr > Issue Type: Improvement > Components: clients - ruby - flare >Affects Versions: 1.3 >Reporter: ian connor > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-1048) Ids parameter and fl=score throws an exception for wt=json
Ids parameter and fl=score throws an exception for wt=json -- Key: SOLR-1048 URL: https://issues.apache.org/jira/browse/SOLR-1048 Project: Solr Issue Type: Bug Components: search Affects Versions: 1.3 Reporter: Laurent Chavet http://yourHost:8080/solr/select/?ids=YourDocId&version=2.2&start=0&rows=10&indent=on&fl=score,id&q=%2B*:* shows that when using ids= the score for docs is null; when using wt=json: http://yourHost:8080/solr/select/?ids=YourDocId&version=2.2&start=0&rows=10&indent=on&fl=score,id&q=%2B*:*&wt=json that throws a NullPointerException: HTTP Status 500 - null java.lang.NullPointerException at org.apache.solr.search.DocSlice$1.score(DocSlice.java:120) at org.apache.solr.request.JSONWriter.writeDocList(JSONResponseWriter.java:490) at org.apache.solr.request.TextResponseWriter.writeVal(TextResponseWriter.java:140) at org.apache.solr.request.JSONWriter.writeNamedListAsMapWithDups(JSONResponseWriter.java:175) at org.apache.solr.request.JSONWriter.writeNamedList(JSONResponseWriter.java:288) at org.apache.solr.request.JSONWriter.writeResponse(JSONResponseWriter.java:88) at org.apache.solr.request.JSONResponseWriter.write(JSONResponseWriter.java:49) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:257) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:847) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1044) Use Hadoop RPC for inter Solr communication
[
https://issues.apache.org/jira/browse/SOLR-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679466#action_12679466
]
Mike Klaas commented on SOLR-1044:
--
{quote} I haven't yet seen a HTTP server serving more than around 1200 req/sec
(apache HTTPD). A call based server can serve 4k-5k messages easily. (I am
yet to test hadoop RPC) . The proliferation of a large no: of frameworks around
that is a testimony to the superiority of that approach. {/quote}
up to 50,000 req/sec, with keepalive:
http://www.litespeedtech.com/web-server-performance-comparison-litespeed-2.0-vs.html
> Use Hadoop RPC for inter Solr communication
> ---
>
> Key: SOLR-1044
> URL: https://issues.apache.org/jira/browse/SOLR-1044
> Project: Solr
> Issue Type: New Feature
> Components: search
>Reporter: Noble Paul
>
> Solr uses http for distributed search . We can make it a whole lot faster if
> we use an RPC mechanism which is more lightweight/efficient.
> Hadoop RPC looks like a good candidate for this.
> The implementation should just have one protocol. It should follow the Solr's
> idiom of making remote calls . A uri + params +[optional stream(s)] . The
> response can be a stream of bytes.
> To make this work we must make the SolrServer implementation pluggable in
> distributed search. Users should be able to choose between the current
> CommonshttpSolrServer, or a HadoopRpcSolrServer .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
