Hi all,
The vote passes with 7+1s (5 binding +1s).
(* = binding)
+1:
Dongjoon Hyun(*)
Liang-Chi Hsieh(*)
Huaxin Gao(*)
Bo Yang
Xiao Li(*)
Chao Sun(*)
Hussein Awala
+0: None
-1: None
Thanks.
-
To unsubscribe e-mail: dev-unsubs
+1 (non-binding) to using an independent version for the Spark Kubernetes
Operator with a compatibility matrix with Spark versions.
On Fri, Apr 12, 2024 at 5:31 AM L. C. Hsieh wrote:
> Hi all,
>
> Thanks for all discussions in the thread of "Versioning of Spark
> O
Apr 12, 2024 at 9:07 AM Dongjoon Hyun
>>> wrote:
>>>
>>>> +1
>>>>
>>>> Thank you!
>>>>
>>>> I hope we can customize `dev/merge_spark_pr.py` script per repository
>>>> after this PR.
>>>>
>>
gt;>
>>> I hope we can customize `dev/merge_spark_pr.py` script per repository
>>> after this PR.
>>>
>>> Dongjoon.
>>>
>>> On 2024/04/12 03:28:36 "L. C. Hsieh" wrote:
>>> > Hi all,
>>> >
>>> > Than
>> Dongjoon.
>>
>> On 2024/04/12 03:28:36 "L. C. Hsieh" wrote:
>> > Hi all,
>> >
>> > Thanks for all discussions in the thread of "Versioning of Spark
>> > Operator":
>> https://lists.apache.org/thread/zhc7nb2sxm8jjxd
> Dongjoon.
>
> On 2024/04/12 03:28:36 "L. C. Hsieh" wrote:
> > Hi all,
> >
> > Thanks for all discussions in the thread of "Versioning of Spark
> > Operator": https://lists.apache.org/thread/zhc7nb2sxm8jjxdppq8qjcmlf4rcsthh
> >
> &
>
> > Thanks for all discussions in the thread of "Versioning of Spark
> > Operator":
> https://lists.apache.org/thread/zhc7nb2sxm8jjxdppq8qjcmlf4rcsthh
> >
> > I would like to create this vote to get the consensus for versioning
> > of the Sp
+1
Thank you!
I hope we can customize `dev/merge_spark_pr.py` script per repository after
this PR.
Dongjoon.
On 2024/04/12 03:28:36 "L. C. Hsieh" wrote:
> Hi all,
>
> Thanks for all discussions in the thread of "Versioning of Spark
> Operator":
Hi all,
Thanks for all discussions in the thread of "Versioning of Spark
Operator": https://lists.apache.org/thread/zhc7nb2sxm8jjxdppq8qjcmlf4rcsthh
I would like to create this vote to get the consensus for versioning
of the Spark Kubernetes Operator.
The proposal is to use an i
: Wednesday, April 10, 2024 6:14 PM
To: Dongjoon Hyun
Cc: dev@spark.apache.org
Subject: [External] Re: Versioning of Spark Operator
This approach makes sense to me.
If Spark K8s operator is aligned with Spark versions, for example, it
uses 4.0.0 now.
Because these JIRA tickets are not actually
This approach makes sense to me.
If Spark K8s operator is aligned with Spark versions, for example, it
uses 4.0.0 now.
Because these JIRA tickets are not actually targeting Spark 4.0.0, it
will cause confusion and more questions, like when we are going to cut
Spark release,
should we include Spark
Cool, looks like we have two options here.
Option 1: Spark Operator and Connect Go Client versioning independent of
Spark, e.g. starting with 0.1.0.
Pros: they can evolve versions independently.
Cons: people will need an extra step to decide the version when using Spark
Operator and Connect Go Cli
Ya, that would work.
Inevitably, I looked at Apache Flink K8s Operator's JIRA and GitHub repo.
It looks reasonable to me.
Although they share the same JIRA, they choose different patterns per place.
1. In POM file and Maven Artifact, independent version number.
1.8.0
2. Tag is also based on th
> >> Sadly, there is no release at all and no activity since last 6 months.
> > >> It seems to be the first time for Apache Spark community to consider
> > >> these sister repositories (Go and K8s Operator).
> > >>
> > >> https://github.com/apa
t; >>
> > > > >> I took a look at `Apache Spark Connect Go` repo mentioned in the
> > > thread. Sadly, there is no release at all and no activity since last 6
> > > months. It seems to be the first time for Apache Spark community to
> > > consider these s
t;>
> > > >> I took a look at `Apache Spark Connect Go` repo mentioned in the
> > thread. Sadly, there is no release at all and no activity since last 6
> > months. It seems to be the first time for Apache Spark community to
> > consider these sister repositories (G
er/
> > >>
> > >> Dongjoon.
> > >>
> > >> On 2024/04/08 17:48:18 "L. C. Hsieh" wrote:
> > >> > Hi all,
> > >> >
> > >> > We've opened the dedicated repository of Spark Kubernetes Ope
k community to consider these
> >> sister repositories (Go and K8s Operator).
> >>
> >> https://github.com/apache/spark-connect-go/commits/master/
> >>
> >> Dongjoon.
> >>
> >> On 2024/04/08 17:48:18 "L. C. Hsieh"
Dongjoon.
>>
>> On 2024/04/08 17:48:18 "L. C. Hsieh" wrote:
>> > Hi all,
>> >
>> > We've opened the dedicated repository of Spark Kubernetes Operator,
>> > and the first PR is created.
>> > Thank you for the review from the co
Operator,
> > and the first PR is created.
> > Thank you for the review from the community so far.
> >
> > About the versioning of Spark Operator, there are questions.
> >
> > As we are using Spark JIRA, when we are going to merge PRs, we need to
> > choose
reated.
> Thank you for the review from the community so far.
>
> About the versioning of Spark Operator, there are questions.
>
> As we are using Spark JIRA, when we are going to merge PRs, we need to
> choose a Spark version. However, the Spark Operator is versioning
> differ
Hi all,
We've opened the dedicated repository of Spark Kubernetes Operator,
and the first PR is created.
Thank you for the review from the community so far.
About the versioning of Spark Operator, there are questions.
As we are using Spark JIRA, when we are going to merge PRs, we need to
c
22 matches
Mail list logo
