Hi Igniters,
I would be happy to serve this role, but since my day job current projects
not related to Ignite, it may cause some delays in replies.
I would give my +1 to both candidates, but I'm concerned how keeping PMC
Chair inside the company initially donated code to ASF could move the
commun
Hi,
I looked into the way Apache Bahir manages their extensions for Spark and
Flink and it looks like they are much independent in terms of managing
their releases. They also have separate git repos for apache bahir and
apache bahir-flink.
Releases :
https://bahir.apache.org/downloads/spark/
http
+1 Alexey Goncharuk
--
Nikita Ivanov
> On Oct 21, 2019, at 10:21 PM, Denis Magda wrote:
>
> Igniters,
>
> It’s been almost 3 years since my election as the PMC Chair and I’d like
> the community to give other PMC members an opportunity to serve in this
> role. It’s healthy to rotate the role
Hi Denis,
Thank you for your response. Yes, I have created the following discussion
thread for Ignite extensions migration.
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html
Regards,
Saikat
O
Folks,
Any other candidates or opinions before I start the vote?
-
Denis
On Tue, Oct 22, 2019 at 2:33 AM Ilya Kasnacheev
wrote:
> Hello!
>
> +1 to all three :)
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 22 окт. 2019 г. в 09:24, Ivan Pavlukhin :
>
> > IMHO, today Dmitriy Pavlov is the best
Folks,
How about considering the option Dmitriy named as "0. placing integration
in a separate module within space of Apache Ignite"?
Nothing prevents us from following concepts of Bahir project in the sense
that we'll be creating and managing separate repositories for Ignite
extensions/modules b
Hi all,
I come from the Pub/Sub integration [1] thread.
I had a check on Bahir and making an implementation there would be nice.
My concern is if Bahir's description limits the choices on a connector
implementation.
'Apache Bahir provides extensions to multiple distributed analytic
platforms, exte
Hi, Saikat, Alexey,
Actually we have 3 ways to solve it.
0. placing integration in a separate module within space of Apache Ignite
1. Apache Bahir
2. Apache Incubator
I'm not sure if option 2 is the best one since it is more about building a
new community around Ignite Extensions, it may be trick
The only issue with the Spark integration tests - they should be runned under
JDK8.
That's all.
I wrote about it recently [1]
[1]
http://apache-ignite-developers.2346864.n4.nabble.com/Spark-examples-on-TC-td43591.html
В Ср, 23/10/2019 в 17:46 +0200, Alexey Zinoviev пишет:
> Good point, now the
Good point, now they are not in the Best state, we have a few ideas how to
fix, will discuss it later here in this thread.
If you have any objection write it, but my position - creation special
Spark Visa on TC, like for ML, maybe two for different Spark versions, and
all commits to Spark will req
Alexander Lapin created IGNITE-12326:
Summary: JDBC thin returns java.util.Date instead of java.sql.Date
if input values, putted to cache via cache API are LocalDate or java.sql.Date.
Key: IGNITE-12326
URL: h
Ok, no objections
On Wed, Oct 23, 2019 at 4:36 PM Alexandr Shapkin wrote:
> Pavel,
>
> I think that in some cases milliseconds could make sense,
> so I would like to keep the current precision.
>
> With this approach we will avoid unnecessary code changes as well as
> keeping API in consistence
Actually, I meant running tests on TeamCity.
ср, 23 окт. 2019 г. в 15:36, Alexey Zinoviev :
>
> What kind of testing do you mean? JUnit, integration via example or
> something else?
>
> ср, 23 окт. 2019 г., 14:16 Ivan Pavlukhin :
>
> > Correction.
> >
> > How are you going to TEST integrations wi
Pavel,
I think that in some cases milliseconds could make sense,
so I would like to keep the current precision.
With this approach we will avoid unnecessary code changes as well as
keeping API in consistence with the thick client method and cacheConfiguration
settings.
From: Pavel Tupitsyn
S
Pavel Kovalenko created IGNITE-12325:
Summary: GridCacheMapEntry reservation mechanism is broken with
enabled cache store
Key: IGNITE-12325
URL: https://issues.apache.org/jira/browse/IGNITE-12325
What kind of testing do you mean? JUnit, integration via example or
something else?
ср, 23 окт. 2019 г., 14:16 Ivan Pavlukhin :
> Correction.
>
> How are you going to TEST integrations with different Spark versions?
>
> ср, 23 окт. 2019 г. в 15:16, Ivan Pavlukhin :
> >
> > Alexey,
> >
> > Thank
Correction.
How are you going to TEST integrations with different Spark versions?
ср, 23 окт. 2019 г. в 15:16, Ivan Pavlukhin :
>
> Alexey,
>
> Thank you for sharing the summary!
>
> Small question. How are you going to integrations with different Spark
> versions?
>
> чт, 17 окт. 2019 г. в 22:3
Alexey,
Thank you for sharing the summary!
Small question. How are you going to integrations with different Spark versions?
чт, 17 окт. 2019 г. в 22:30, Denis Magda :
>
> >
> > 1. We are going to release Apache Ignite 2.8 with limited support of
> >Spark 2.4.4 (known issues are listed here
18 matches
Mail list logo
