[
https://issues.apache.org/jira/browse/ACCUMULO-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14214795#comment-14214795
]
Josh Elser commented on ACCUMULO-3338:
--------------------------------------
bq. We do not include vendor specific paths for any other distribution and I
don't think we should start now.
We already have made the decision, and have code included in Apache Accumulo,
that vendor specific changes are acceptable if someone takes the time to make a
vendor specific change. Note: o.a.a.s.m.recovery.MapRLogCloser. I don't see a
reason why configuration files should be treated differently than source code.
bq. I've run into many many cases where users treat the example configurations
as appropriate for production use
That may be the case, but I don't believe that's actually feasible to
accomplish. I don't know how it's possible to provide an out of the box
configuration file or configuration script which is actually secure.
Additionally, this change did not initially introduce this, but continued the
practice of having these example configurations work with HDP's layout
({{/usr/lib/hadoop-hdfs}}, and others are HDP specific).
> Update example classpath configuration
> --------------------------------------
>
> Key: ACCUMULO-3338
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3338
> Project: Accumulo
> Issue Type: Improvement
> Components: docs
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Trivial
> Fix For: 1.6.2, 1.7.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Make sure the example configuration general.classpaths contain some extra
> paths for HDFS jars which make them more likely to generally work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)