[jira] [Commented] (ACCUMULO-1635) Support external configuration in client API

["Keith Turner (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ACCUMULO-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727978#comment-13727978 ] 

Keith Turner commented on ACCUMULO-1635:
----------------------------------------

This change may necessitate some API changes.   For example the following call forces the user to pass the number of threads.  A call like this would need to be changed, so the number of threads can optionally be supplied.

{code:java}
   public abstract BatchScanner createBatchScanner(String tableName, Authorizations authorizations, int numQueryThreads) throws TableNotFoundException;
{code}
                
> Support external configuration in client API
> --------------------------------------------
>
>                 Key: ACCUMULO-1635
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1635
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Keith Turner
>             Fix For: 1.6.0
>
>
> Currently things like timeout, batch writer max mem, etc are only configurable in the API by making method calls.  It would be nice if a user could pass a config file to the connector that provides default configutations for things like timeout, batch writer max memory, etc.
> Since Accumulo is used on a cluster, in addition to a config file, supporting configuration profiles in zookeeper would also be nice.  For example I can tell my application to use configuration profile X in zookeeper.   If I do not specify a batch writer max mem, then it will look in the configuration profile in zookeeper.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira