here:
> >
> > https://issues.apache.org/jira/browse/BIGTOP-1480
> >
> >
> >
> > -Original Message-
> > From: Sean Owen [mailto:so...@cloudera.com]
> > Sent: Monday, February 9, 2015 3:52 PM
> > To: Nicholas Chammas
> > Cc: Patric
age-
> > From: Sean Owen [mailto:so...@cloudera.com]
> > Sent: Monday, February 9, 2015 3:52 PM
> > To: Nicholas Chammas
> > Cc: Patrick Wendell; Mark Hamstra; dev
> > Subject: Re: Keep or remove Debian packaging in Spark?
> >
> > What about this straw ma
t; Sent: Monday, February 9, 2015 3:52 PM
> To: Nicholas Chammas
> Cc: Patrick Wendell; Mark Hamstra; dev
> Subject: Re: Keep or remove Debian packaging in Spark?
>
> What about this straw man proposal: deprecate in 1.3 with some kind of
> message in the build, and remove for
: Sean Owen [mailto:so...@cloudera.com]
Sent: Monday, February 9, 2015 3:52 PM
To: Nicholas Chammas
Cc: Patrick Wendell; Mark Hamstra; dev
Subject: Re: Keep or remove Debian packaging in Spark?
What about this straw man proposal: deprecate in 1.3 with some kind of message
in the build, and remove for
What about this straw man proposal: deprecate in 1.3 with some kind of
message in the build, and remove for 1.4? And add a pointer to any
third-party packaging that might provide similar functionality?
On Mon, Feb 9, 2015 at 6:47 PM, Nicholas Chammas
wrote:
> +1 to an "official" deprecation + red
+1 to an "official" deprecation + redirecting users to some other project
that will or already is taking this on.
Nate?
On Mon Feb 09 2015 at 10:08:27 AM Patrick Wendell
wrote:
> I have wondered whether we should sort of deprecated it more
> officially, since otherwise I think people have the
I have wondered whether we should sort of deprecated it more
officially, since otherwise I think people have the reasonable
expectation based on the current code that Spark intends to support
"complete" Debian packaging as part of the upstream build. Having
something that's sort-of maintained but n
>
> it sounds like nobody intends these to be used to actually deploy Spark
I wouldn't go quite that far. What we have now can serve as useful input
to a deployment tool like Chef, but the user is then going to need to add
some customization or configuration within the context of that tooling to
This is a straw poll to assess whether there is support to keep and
fix, or remove, the Debian packaging-related config in Spark.
I see several oldish outstanding JIRAs relating to problems in the packaging:
https://issues.apache.org/jira/browse/SPARK-1799
https://issues.apache.org/jira/browse/SP
