[
https://issues.apache.org/jira/browse/ACCUMULO-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683879#comment-13683879
]
Christopher Tubbs commented on ACCUMULO-1488:
---------------------------------------------
[~afuchs], please don't trivialize the amount of time spent discussing the
issue. It's important to gather consensus through discussions that present
different views, and this particular concern about back-porting relates to
setting a larger precedent for back-porting in the future. If we end the
conversation without a consensus, we will continue to have these kinds of
exchanges *every* time somebody sneaks in a feature into the bugfix branch of a
prior release, not just this relatively-tiny addition.
Regarding the problem of supporting a jar outside the main branch, I think
you're exaggerating the costs of adding a jar to the lib directory. I use
additional iterators often enough, and find it relatively trivial to include
them as an add-on. I'm even using the Lexicoders from [~kturner]'s
[Typo|https://github.com/keith-turner/typo] when I run Accumulo 1.5.0
instances, and think it's perfectly reasonable to continue to do so while I
wait for their full inclusion in the 1.6.0 release.
Further, I don't find it essential that *every* iterator need to be included as
soon as possible, or even at all, whether it be created by users or
core-developers, and I don't think you've made a compelling case to urgently
include these particular ones, sufficient to justify the maintenance and
potential user-confusion costs of back-porting this feature to a maintenance
release branch. All you've done is *state* that you have done this risk
assessment and have determined it justifiable. You have not actually
*presented* that justification. This is fine, of course, since we haven't
(evidently) reached consensus on back-porting features, and we're operating on
lazy consensus. However, since its inclusion has been questioned, I would hope
that you would at least be willing to try to present a justification at this
time.
And finally, you still haven't addressed the concerns I've expressed here and
Keith [has expressed on the mailing list (objection
#4)|http://mail-archives.apache.org/mod_mbox/accumulo-dev/201305.mbox/%3ccagutchrqp6kx+xe1m97uvs75+ya6+urbvk6hqw+kuycxx10...@mail.gmail.com%3E]
regarding the "at least wait until it's been finalized in a released version
before back-porting" concept.
> support BigDecimal encoding for basic built-in combiners
> --------------------------------------------------------
>
> Key: ACCUMULO-1488
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1488
> Project: Accumulo
> Issue Type: New Feature
> Reporter: Adam Fuchs
> Fix For: 1.5.1, 1.6.0
>
> Attachments: ACCUMULO-1488.patch
>
>
> Support sum, min, and max operations for decimal numbers using the
> java.math.BigDecimal String encoding and decoding functions
> (BigDecimal.toString() and BigDecimal(String)).
--
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
