Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/682
I didn't get a chance to review/vote on this before it was merged, but I
dont' think this is what I expected to happen when I wrote the JIRA. I didn't
think we would produce direct support for `BigDecimal` so much as coerce
`BigDecimal` into double so that when Groovy did its magic to:
```groovy
g.withSack(2).V().sack(Operator.div).by(constant(3.0)).sack()
```
we'd just get back a double - not a `BigDecimal`. Directly supporting
`BigDecimal` means we need to support it as a GraphSON type. We already do, but
only in the extended module so if you wanted to use `BigDecimal` you'd have to
include that configuration. No GLV at this point supports the extended module
(though @davebshow is working on that). Do we really need to provide direct
support for `BigDecimal` when the problem we were trying to solve was related
to Groovy taking a literal and auto-assigning it to `BigDecimal` (sorta
unexpected)? or do users really need the ability to do
`constant(BigDecimal.valueOf(3))`?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
