There would be records in millions and field would only be md5 hash. Size of field would be 32 chars
Can you please point out what would be the best approach ? Thanks On Sep 5, 2014 12:47 PM, "Mikhail Khludnev" <mkhlud...@griddynamics.com> wrote: > Hello, > > You are asking without giving a context. What's the size of sets, desired > TPS, key length, and even values? > It's hard to answer definitely. It's not primary usage for Lucene, it adds > some unnecessary overhead. However, community collected a few workaround > for such kind of problem. From the other side, as far as I know executing > queries like WHERE x IN (1,....,2324) is not a piece of cake for SQL > servers, also. > > you can follow link at > https://plus.google.com/u/0/+MichaelMcCandless/posts/8VNydNi3wvK to find a > relevant benchmark. it might help you to get least estimates for the Lucene > solution. > > > > On Thu, Sep 4, 2014 at 5:53 PM, Mark , N <nipen.m...@gmail.com> wrote: > > > I have a use-case where we want to store unique keys ( Hashes) which > would > > be > > used to compare against another set of keys ( Hashes) > > > > For example > > > > Index set= { h1, h2 , h3 , h4 } > > > > comparision set = { h1 , h2 } > > > > result set = h1,h2 > > > > Would it be an advantage to store "index set" in Solr instead of storing > > in traditional databases? > > > > Thanks in advance > > > > > > > > > > > > > > *Nipen Mark * > > > > > > -- > Sincerely yours > Mikhail Khludnev > Principal Engineer, > Grid Dynamics > > <http://www.griddynamics.com> > <mkhlud...@griddynamics.com> >
