[
https://issues.apache.org/jira/browse/BIGTOP-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849799#comment-13849799
]
Konstantin Boudnik commented on BIGTOP-1097:
--------------------------------------------
Jay, this is a long going conversation and the reason we need Groovy is things
like BIGTOP-952. Working with Java stack via shell-outs is very suboptimal to
say the least. Instead we can do things directly via HDFS/MR/YARN/Hbase APIs if
needed. I'd suggest to search through the dev@ archive on the discussion.
> introduce bigtop-groovy package
> -------------------------------
>
> Key: BIGTOP-1097
> URL: https://issues.apache.org/jira/browse/BIGTOP-1097
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.6.0
> Reporter: Roman Shaposhnik
> Assignee: Konstantin Boudnik
> Fix For: 0.8.0
>
>
> Bigtop platform depends on groovy extensively and we see a trend to introduce
> new functionality into the cluster deployment, etc. that will greatly benefit
> from the presence of a dynamic, functional scripting language on top of JVM.
> Hence, it makes sense to provide Groovy runtime environment as a part of
> Bigtop installable stack (e.g. think of bigtop-utils type of package). It
> will be lightweight and only needs to include a couple of jar files from a
> standard Groovy distribution. There's no need to build Groovy from scratch
> but just download the binary archive, extract jars we need, and wrap them
> into a Linux package.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
