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

Linbin Chen updated SOLR-1197:
------------------------------

    Attachment: SOLR_1197-solr-memcache-0.2.patch

solr sint hashcode conflict cause solr memcached bug

solr-memcached-0.2

solr sint fieldType sint.hashcode conflict very hight above 99%

such as id:44232808 and id:44090533 hashcode conflict, so q=id:44232808 
maybe response id:44090533 doc result. error!

http://code.google.com/p/solr-side/issues/detail?id=2&can=1
solr-memcached-0.2 patch for create memcache key strategy:

QueryResultKey add method

  public String toString() {
          return query.toString();
  }

for MemcachedCache md5(QueryResultKey.toString())

now memcache key strategy = 
md5(keyPrefix+indexVersion+QueryResultKey.hashCode()+md5(QueryResultKey.toString()))

double md5

solr-memcache-0.2.zip 
http://solr-side.googlecode.com/files/solr-memcache-0.2.zip


> memcached implement solr cache for queryresultCache 
> ----------------------------------------------------
>
>                 Key: SOLR-1197
>                 URL: https://issues.apache.org/jira/browse/SOLR-1197
>             Project: Solr
>          Issue Type: New Feature
>    Affects Versions: 1.3
>         Environment: multiple slave solr replication environment
>            Reporter: Linbin Chen
>            Assignee: Noble Paul
>             Fix For: 1.5
>
>         Attachments: SOLR_1197-solr-memcache-0.2.patch, 
> SOLR_1197-solr-memcache.patch
>
>
> multiple slave create query result together, and slaves can share that.
> implement  memcached cache instead LRUCache
> my implement:
> solr-memcache.zip http://solr-side.googlecode.com/files/solr-memcache.zip 
> object transport by net need Serializable, so need patch solr 1.3, DocSetBase 
> implements Serializable, see 
> http://code.google.com/p/solr-side/issues/detail?id=1&can=1

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

Reply via email to