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

Jonathan Hsieh commented on ACCUMULO-1576:
------------------------------------------

[~mdrob], the continuous tests have two types of config files -- host list 
files (walkers.txt, ingesters.txt etc) and the continuous-env.sh(.example) 
config script.   Currently the continuous tests always run using the values set 
in the test/system/continuous directory.  These config files are different than 
the files traditionally found in accumulo/conf (ACCUMULO_CONF_DIR after 
ACCUMULO-1550..).

If we used the same ACCUMULO_CONF_DIR value, all the walkers/ingesters list 
files and the continuous-env.sh would need to be in ACCUMULO_CONF_DIR.  Keeping 
them separate keeps them decoupled.  CONTINUOUS_CONF_DIR could be set to 
ACCUMULO_CONF_DIR or defaulted to it but in these patches I just picked the 
defaulting to the existing paths.  If we force them to be the same, we would 
have to have multiple copies of accumulo conf files if we wanted different 
continuous test config files.
                
> add CONTINUOUS_CONF_DIR environment variable for continuous ingest test
> -----------------------------------------------------------------------
>
>                 Key: ACCUMULO-1576
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1576
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 1.4.3, 1.5.0
>            Reporter: Jonathan Hsieh
>            Assignee: Jonathan Hsieh
>         Attachments: accumulo-1576-1.4.patch, accumulo-1576.patch
>
>
> This is similar to ACCUMULO-1550 -- the idea is to have an environment 
> variable that allows continuous ingest tests' configs to be decoupled from 
> the specific location.  Different runs can now just point to different config 
> dirs without file system modification.

--
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

Reply via email to