[jira] [Created] (PIRK-75) Improve handling of exponent look up tables

["Tim Ellison (JIRA)" <ji...@apache.org>]

Tim Ellison created PIRK-75:
-------------------------------

             Summary: Improve handling of exponent look up tables
                 Key: PIRK-75
                 URL: https://issues.apache.org/jira/browse/PIRK-75
             Project: PIRK
          Issue Type: Improvement
          Components: Responder
            Reporter: Tim Ellison
            Assignee: Tim Ellison


Presently, Pirk has the ability to create exponent tables for a query
either in memory directly via the Query#expTable (which ends up being a
map of maps element -> <power, element^power mod N^2>), or using
map-reduce on HDFS via Query#expFileBasedLookup (which ends up being
element hash -> filename containing <power, element^power mod N^2>
strings, and back in memory as a Guava cache).

This task is to pull these table representations out to a core abstract
type that provides the exponent table calls, and create the concrete
implementations under there.  Then all the table building and lookup
would be in one place, and a Query would just have one expTable
reference to worry about.

The advantages would be in the responders (who currently have to know about in memory and HDFS based tables) and the query API (that also has to specify whether to use these tables).  It would also allow for easier experimentation with different types of exponent caching to determine the best for a particular type of responder.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)