I wanted to revive the conversation about the spark-ec2 tools, as it seems
to have been lost in the 1.4.1 release voting spree.
I think that splitting it into its own repository is a really good move,
and I would also be happy to help with this transition, as well as help
maintain the resulting re
gt;>> 5. Triage open JIRAs to the new repo's issue tracker and close them
>>> elsewhere
>>> 6. Remove the old copies of the code and leave a pointer to the new
>>> location in their place
>>>
>>> I'd also like to hear a few more nods befor
I think that is a good idea, and slated to happen. At the very least a
README or some such. Is this a use case for git submodules? I am
considering porting some of this to a more general spark-cloud launcher,
including google/aliyun/rackspace. It shouldn't be hard at all given the
current appro
I would tentatively suggest also conda packaging.
http://conda.pydata.org/docs/
--Matthew Goodman
=
Check Out My Website: http://craneium.net
Find me on LinkedIn: http://tinyurl.com/d6wlch
On Mon, Aug 10, 2015 at 11:23 AM, Davies Liu wrote:
> I think so, any contributions
