accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1576) add CONTINUOUS_CONF_DIR environment variable for continuous ingest test
Date Wed, 17 Jul 2013 15:24:49 GMT


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

View raw message