accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3178) Create example preferred volumes chooser
Date Wed, 22 Oct 2014 14:18:33 GMT


Sean Busbey commented on ACCUMULO-3178:

While I agree that being present in configuration sets user expectations, that's not the same
as the class itself being in the public API. The public API has implications for maintaining
compatibility for those programming in the JVM. Compatibility at that level could be broken
in many ways while maintaining the exposed configuration with built in members; even class
names could change because we can just do a mapping of the configuration string in older instances.

FWIW, I treat all of the server side customization points as "here there be dragons" and would
advocate against making them public API because that constrains us too much in how we implement
things. That isn't to say we should just change them willy nilly but they are advanced uses
for a reason, including a higher operational burden because the API might change. Presuming
we have a DISCUSS thread at some point, we should probable consider including a LimitedPrivate
advisory designation (similar to [the ones HBase has for e.g. coprocessors, replication, and

> Create example preferred volumes chooser
> ----------------------------------------
>                 Key: ACCUMULO-3178
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: Jenna Huston
>            Assignee: Jenna Huston
> This example VolumeChooser chooses a volume from a user specified list of preferred volumes
for that specific table.

This message was sent by Atlassian JIRA

View raw message