[jira] Commented: (SOLR-1316) Create autosuggest component

2009-11-19 Thread Mike Anderson (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780435#action_12780435
 ] 

Mike Anderson commented on SOLR-1316:
-

Two questions, and apologies if they are addressed in the patches themselves:

1) Will this be supported on distributed setups?

2) (maybe this is a new ticket) Is it possible to store the field name in the 
spellcheck index. The use case for this is: I create a dictionary from the 
'person' field and the 'title' field, when using autosuggest it would be nice 
to separate suggestions into 'person' suggestions and 'title' suggestions.

> Create autosuggest component
> 
>
> Key: SOLR-1316
> URL: https://issues.apache.org/jira/browse/SOLR-1316
> Project: Solr
>  Issue Type: New Feature
>  Components: search
>Affects Versions: 1.4
>Reporter: Jason Rutherglen
>Priority: Minor
> Fix For: 1.5
>
> Attachments: suggest.patch, suggest.patch, TST.zip
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> Autosuggest is a common search function that can be integrated
> into Solr as a SearchComponent. Our first implementation will
> use the TernaryTree found in Lucene contrib. 
> * Enable creation of the dictionary from the index or via Solr's
> RPC mechanism
> * What types of parameters and settings are desirable?
> * Hopefully in the future we can include user click through
> rates to boost those terms/phrases higher

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (SOLR-1550) statistics for request handlers should report std dev

2009-11-09 Thread Mike Anderson (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mike Anderson updated SOLR-1550:


Attachment: (was: SOLR-1550.patch)

> statistics for request handlers should report std dev
> -
>
> Key: SOLR-1550
> URL: https://issues.apache.org/jira/browse/SOLR-1550
> Project: Solr
>  Issue Type: Improvement
>Reporter: Mike Anderson
>Priority: Trivial
> Attachments: SOLR-1550.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (SOLR-1550) statistics for request handlers should report std dev

2009-11-09 Thread Mike Anderson (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mike Anderson updated SOLR-1550:


Attachment: SOLR-1550.patch

tabs to spaces and cleaned up.

> statistics for request handlers should report std dev
> -
>
> Key: SOLR-1550
> URL: https://issues.apache.org/jira/browse/SOLR-1550
> Project: Solr
>  Issue Type: Improvement
>Reporter: Mike Anderson
>Priority: Trivial
> Attachments: SOLR-1550.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (SOLR-1550) statistics for request handlers should report std dev

2009-11-09 Thread Mike Anderson (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mike Anderson updated SOLR-1550:


Attachment: SOLR-1550.patch

I followed this algorithm: 
http://en.wikipedia.org/wiki/Standard_deviation#Rapid_calculation_methods

Somebody should double check the type casting, though, I just made educated 
guesses. I couldn't find the unit tests for these statistics, if somebody could 
point me in the right direction I can write one.


Cheers,
Mike

> statistics for request handlers should report std dev
> -
>
> Key: SOLR-1550
> URL: https://issues.apache.org/jira/browse/SOLR-1550
> Project: Solr
>  Issue Type: Improvement
>Reporter: Mike Anderson
>Priority: Trivial
> Attachments: SOLR-1550.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (SOLR-1550) statistics for request handlers should report std dev

2009-11-09 Thread Mike Anderson (JIRA)
statistics for request handlers should report std dev
-

 Key: SOLR-1550
 URL: https://issues.apache.org/jira/browse/SOLR-1550
 Project: Solr
  Issue Type: Improvement
Reporter: Mike Anderson
Priority: Trivial




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SOLR-1143) Return partial results when a connection to a shard is refused

2009-11-02 Thread Mike Anderson (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772681#action_12772681
 ] 

Mike Anderson commented on SOLR-1143:
-

What's the current state of this use case? I have a shard that is a slower than 
all the others and I'd rather just get partial (or no) results back from the 
slow shard instead of slowing down the whole operation. 

I've looked over SOLR-1143, SOLR-502, and SOLR-850 but I'm not exactly sure how 
they all tie together and what's available from trunk today. 

I tried setting timeAllowed to something really small like 5, but I still got 
back all of the results I got when timeAllowed wasn't set (I would have 
expected no results). 

-mike

> Return partial results when a connection to a shard is refused
> --
>
> Key: SOLR-1143
> URL: https://issues.apache.org/jira/browse/SOLR-1143
> Project: Solr
>  Issue Type: Improvement
>  Components: search
>Reporter: Nicolas Dessaigne
>Assignee: Grant Ingersoll
> Fix For: 1.5
>
> Attachments: SOLR-1143-2.patch, SOLR-1143-3.patch, SOLR-1143.patch
>
>
> If any shard is down in a distributed search, a ConnectException it thrown.
> Here's a little patch that change this behaviour: if we can't connect to a 
> shard (ConnectException), we get partial results from the active shards. As 
> for TimeOut parameter (https://issues.apache.org/jira/browse/SOLR-502), we 
> set the parameter "partialResults" at true.
> This patch also adresses a problem expressed in the mailing list about a year 
> ago 
> (http://www.nabble.com/partialResults,-distributed-search---SOLR-502-td19002610.html)
> We have a use case that needs this behaviour and we would like to know your 
> thougths about such a behaviour? Should it be the default behaviour for 
> distributed search?

-- 
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-788) MoreLikeThis should support distributed search

2009-09-01 Thread Mike Anderson (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750158#action_12750158
 ] 

Mike Anderson edited comment on SOLR-788 at 9/1/09 3:38 PM:


I had trouble getting this to work in my distributed setup so I changed the 
patch around (for better or worse) to make it flow in a way that made sense to 
me.

Just wanted to post in case anybody else was having trouble.


Some thoughts on response builder/ distributed components: It would be nice to 
allow components to add requests (in a natural way)  to response builder after 
the QueryComponent has made it through finishedStage and merged all the 
results. This could optimize MLT so that instead of finding MLT for the top 5 
hits from each shard, we find MLT for the top 5 hits overall. (maybe there's a 
way to do this, but I couldn't really find the intuition behind it) .

(attached patch is a modified version of Matt's)

mike
mik...@mit.edu

  was (Author: cambridgemike):
I had trouble getting this to work in my distributed setup so I changed the 
patch around (for better or worse) to make it flow in a way that made sense to 
me.

Just wanted to post in case anybody else was having trouble.


Some thoughts on response builder/ distributed components: It would be nice to 
allow components to add requests (in a natural way)  to response builder after 
the QueryComponent has made it through finishedStage and merged all the 
results. This could optimize MLT so that instead of finding MLT for the top 5 
hits from each shard, we find MLT for the top 5 hits overall. (maybe there's a 
way to do this, but I couldn't really find the intuition behind it) .

mike
mik...@mit.edu
  
> MoreLikeThis should support distributed search
> --
>
> Key: SOLR-788
> URL: https://issues.apache.org/jira/browse/SOLR-788
> Project: Solr
>  Issue Type: Improvement
>Reporter: Grant Ingersoll
>Priority: Minor
> Attachments: AlternateDistributedMLT.patch, 
> MoreLikeThisComponentTest.patch, SolrMoreLikeThisPatch.txt
>
>
> The MoreLikeThis component should support distributed processing.
> See SOLR-303.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (SOLR-788) MoreLikeThis should support distributed search

2009-09-01 Thread Mike Anderson (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mike Anderson updated SOLR-788:
---

Attachment: AlternateDistributedMLT.patch

I had trouble getting this to work in my distributed setup so I changed the 
patch around (for better or worse) to make it flow in a way that made sense to 
me.

Just wanted to post in case anybody else was having trouble.


Some thoughts on response builder/ distributed components: It would be nice to 
allow components to add requests (in a natural way)  to response builder after 
the QueryComponent has made it through finishedStage and merged all the 
results. This could optimize MLT so that instead of finding MLT for the top 5 
hits from each shard, we find MLT for the top 5 hits overall. (maybe there's a 
way to do this, but I couldn't really find the intuition behind it) .

mike
mik...@mit.edu

> MoreLikeThis should support distributed search
> --
>
> Key: SOLR-788
> URL: https://issues.apache.org/jira/browse/SOLR-788
> Project: Solr
>  Issue Type: Improvement
>Reporter: Grant Ingersoll
>Priority: Minor
> Attachments: AlternateDistributedMLT.patch, 
> MoreLikeThisComponentTest.patch, SolrMoreLikeThisPatch.txt
>
>
> The MoreLikeThis component should support distributed processing.
> See SOLR-303.

-- 
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-788) MoreLikeThis should support distributed search

2009-08-19 Thread Mike Anderson (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745079#action_12745079
 ] 

Mike Anderson edited comment on SOLR-788 at 8/19/09 9:00 AM:
-

Yep, I got that part figured out finally. Unfortunately I'm getting back 0 
results when I pass the shards parameter, as opposed to when it is omited.

http://localhost:8983/solr/select?q=graph&mlt=true&mlt.fl=title&mlt.mindf=1&mlt.mintf=1&fl=id,score,title&shards=localhost:8983/solr

returns:





where as 

http://localhost:8983/solr/select?q=graph&mlt=true&mlt.fl=title&mlt.mindf=1&mlt.mintf=1&fl=id,score,title

returns



   ...result docs

  ...result docs


However, perhaps more pressing is that when the shards param is set my 
spellCheck component stops responding (I had to apply the distributed 
spellcheck patch as well). yikes...

I poked around in the code, but couldn't really make any progress.. Any help 
would be greatly appreciated.

-mike

  was (Author: cambridgemike):
Yep, I got that part figured out finally. Unfortunately I'm getting back 0 
results when I pass the shards parameter, as opposed to when it is omited.

http://localhost:8983/solr/select?q=graph&mlt=true&mlt.fl=title&mlt.mindf=1&mlt.mintf=1&fl=id,score,title&shards=localhost:8983/solr

returns:





where as 

http://localhost:8983/solr/select?q=graph&mlt=true&mlt.fl=title&mlt.mindf=1&mlt.mintf=1&fl=id,score,title

returns



   ...result docs

  ...result docs



I poked around in the code, but couldn't really make any progress.. Any help 
would be greatly appreciated.

-mike
  
> MoreLikeThis should support distributed search
> --
>
> Key: SOLR-788
> URL: https://issues.apache.org/jira/browse/SOLR-788
> Project: Solr
>  Issue Type: Improvement
>Reporter: Grant Ingersoll
>Priority: Minor
> Attachments: MoreLikeThisComponentTest.patch, 
> SolrMoreLikeThisPatch.txt
>
>
> The MoreLikeThis component should support distributed processing.
> See SOLR-303.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SOLR-788) MoreLikeThis should support distributed search

2009-08-19 Thread Mike Anderson (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745079#action_12745079
 ] 

Mike Anderson commented on SOLR-788:


Yep, I got that part figured out finally. Unfortunately I'm getting back 0 
results when I pass the shards parameter, as opposed to when it is omited.

http://localhost:8983/solr/select?q=graph&mlt=true&mlt.fl=title&mlt.mindf=1&mlt.mintf=1&fl=id,score,title&shards=localhost:8983/solr

returns:





where as 

http://localhost:8983/solr/select?q=graph&mlt=true&mlt.fl=title&mlt.mindf=1&mlt.mintf=1&fl=id,score,title

returns



   ...result docs

  ...result docs



I poked around in the code, but couldn't really make any progress.. Any help 
would be greatly appreciated.

-mike

> MoreLikeThis should support distributed search
> --
>
> Key: SOLR-788
> URL: https://issues.apache.org/jira/browse/SOLR-788
> Project: Solr
>  Issue Type: Improvement
>Reporter: Grant Ingersoll
>Priority: Minor
> Attachments: MoreLikeThisComponentTest.patch, 
> SolrMoreLikeThisPatch.txt
>
>
> The MoreLikeThis component should support distributed processing.
> See SOLR-303.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SOLR-788) MoreLikeThis should support distributed search

2009-08-17 Thread Mike Anderson (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744233#action_12744233
 ] 

Mike Anderson commented on SOLR-788:


What release of SOLR should one apply this patch to? 


(I tried an older build of 1.4 and got
patching file org/apache/solr/handler/MoreLikeThisHandler.java
patching file org/apache/solr/handler/component/MoreLikeThisComponent.java
Hunk #2 FAILED at 51.
1 out of 2 hunks FAILED -- saving rejects to file 
org/apache/solr/handler/component/MoreLikeThisComponent.java.rej
patching file org/apache/solr/handler/component/ShardRequest.java
)

> MoreLikeThis should support distributed search
> --
>
> Key: SOLR-788
> URL: https://issues.apache.org/jira/browse/SOLR-788
> Project: Solr
>  Issue Type: Improvement
>Reporter: Grant Ingersoll
>Priority: Minor
> Attachments: MoreLikeThisComponentTest.patch, 
> SolrMoreLikeThisPatch.txt
>
>
> The MoreLikeThis component should support distributed processing.
> See SOLR-303.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.