Hello,
I wanted to connect and discuss on the release process for
ignite-extensions. As of today all our integrations since released together
were able to run build based on latest snapshot for example the current
build depends on 2.8.0-SNAPSHOT. If we are making ignite-extensions as
separate
Hi Denis,
Yes, sure I will start moving each extension one at a time and share
updates.
I am currently working on Flink extension.
Regards,
Saikat
On Tue, Nov 12, 2019 at 1:55 PM Denis Magda wrote:
> Saikat,
>
> Thanks for decoupling the task. Please ping the community once there is
>
Saikat,
Thanks for decoupling the task. Please ping the community once there is
anything ready for a review or a further discussion.
-
Denis
On Sat, Nov 9, 2019 at 3:58 PM Saikat Maitra
wrote:
> Hello,
>
> As discussed I have created the following jira issues for tracking the
> migration
Hello,
As discussed I have created the following jira issues for tracking the
migration work for ignite-extensions.
Main issue : IEP-36: Modularization
https://issues.apache.org/jira/browse/IGNITE-12355
Sub-Tasks
Migrate flink module to ignite-extensions
Ivan, Thank you for initialising the master branch, much appreciate it.
Denis, Emmanouil,
We use both local server and mockito to write the tests for flink. Incase
of sink it is easier to use a local server mode and publish the data into
Ignite Sink where as in case of Ignite used as data source
Hi,
I just took another look at the Kafka Implementation and I realised that it
is a local implementation that is used on the tests (I thought it was a
server already existing somewhere).
It seems I might be able to spin up the Pub/Sub server locally (I found an
official tool which might work),
Saikat, Roman,
What's your thinking? I'm not sure we set any infrastructure to validate
our Kafka or Flink integrations. For instance, for Flink we use Mockito
just to ensure that basic tests pass: https://en.wikipedia.org/wiki/Mockito
Our IP finders for AWS, GCE or K8 don't start up any
Hi all,
That's great news! Yes I am ready to do a pull request on the new repo.
I believe it is ok to create a ticket for the Pub/Sub proposal [1].
My next question has to do with the CI and the integration tests. In order
for my tests to work, a local Pub/Sub server needs to be up and running.
I
Saikat,
I initialized master branch with empty README file [1]. I suppose all
ignite committers have rights for push.
[1] https://github.com/apache/ignite-extensions
пт, 1 нояб. 2019 г. в 08:01, Saikat Maitra :
>
> Hello Dmitriy, Denis
>
> Thank you for help in creating the repo. I can see it
Hello Dmitriy, Denis
Thank you for help in creating the repo. I can see it has synced in github
as well.
Can you please add a sample readme.md file as the repo is empty I am unable
to fork it?
or let me check if I can directly commit a sample readme file from local
then I should be able to fork
Dmitriy, thanks a lot for a quick turnaround! Saikat, please let us know if
anything else is needed.
-
Denis
On Thu, Oct 31, 2019 at 1:12 PM Dmitriy Pavlov wrote:
> Hi, I've created
> https://gitbox.apache.org/repos/asf/ignite-extensions.git
>
> It should be synced in a few minutes.
>
>
Hi, I've created
https://gitbox.apache.org/repos/asf/ignite-extensions.git
It should be synced in a few minutes.
Sincerely,
Dmitriy Pavlov
чт, 31 окт. 2019 г. в 22:58, Denis Magda :
> Ignite PMCs, can anybody create the repo for Saikat? I'm on the road and
> can't do that.
>
> -
> Denis
>
>
>
Ignite PMCs, can anybody create the repo for Saikat? I'm on the road and
can't do that.
-
Denis
On Wed, Oct 30, 2019 at 8:40 PM Saikat Maitra
wrote:
> Hi,
>
> I would need help from Ignite PMC member to create the new
> repository ignite-extensions.
>
> Can you please create the repository
Hi,
I would need help from Ignite PMC member to create the new
repository ignite-extensions.
Can you please create the repository here https://selfserve.apache.org/
Regards,
Saikat
On Wed, Oct 30, 2019 at 10:28 PM Saikat Maitra
wrote:
> Hello Denis,
>
> Thank you for your response.
>
> I
Hello Denis,
Thank you for your response.
I tried to request for new repository but the repository name is showing up
as YourPMCs-ignite-extensions.git. I have reached out to Apache Infra user
email list to understand the process to create a new repository.
I will definitely help to migrate the
"ignite-extensions" might be a better name in the long term if we decide to
place any extension to the repo that doesn't integrate with any 3rd party
technology but rather enhances Ignite with extra API.
After thinking about it for the last few days, I think that the best
approach to start with
Folks,
Just another one name candidate "ignite-integrations"
Or are there not only integrations?
вт, 29 окт. 2019 г. в 03:31, Saikat Maitra :
>
> Hi Denis,
>
> I meant we can create dedicated repository for individual extensions and we
> can create submodules inside each specific repository for
Hi Denis,
I meant we can create dedicated repository for individual extensions and we
can create submodules inside each specific repository for individual
extensions versions.
Regards,
Saikat
On Mon, Oct 28, 2019 at 7:14 PM Saikat Maitra
wrote:
> Hi Denis,
>
> Yes, dedicated repository is
Hi Denis,
Yes, dedicated repository is also a good idea and we can create submodules
inside each specific repository for individual extensions.
Regards,
Saikat
On Mon, Oct 28, 2019 at 2:34 PM Denis Magda wrote:
> Folks,
>
> What do you think about having a dedicated repository for each
Folks,
What do you think about having a dedicated repository for each extension
instead of a single one? It sounds complicated but might be worthwhile for
cases when an integration requires to support several versions. Take Spark
or Hibernate as an example, we already provide different versions
Hello Alexey,
Thank you for your email. Yes, I am also aligned for ignite-extensions.
If others are also ok we can create the new repository with name
ignite-extensions.
Regards,
Saikat
On Sat, Oct 26, 2019 at 3:11 AM Alexey Zinoviev
wrote:
> Vote for ignite-extensions (it's more widely than
Vote for ignite-extensions (it's more widely than ignite-connectors)
сб, 26 окт. 2019 г. в 05:52, Saikat Maitra :
> Hello Denis, Dmitriy
>
> Thank you for your reply. I am thinking when a new repo is created that
> will not mean that the project will undergo Incubator process , Is
> this
Hello Denis, Dmitriy
Thank you for your reply. I am thinking when a new repo is created that
will not mean that the project will undergo Incubator process , Is
this correct?
We actually want to just take few of our integrations and release them
separately as part of this new git repository. We
Hi Denis,
any PMC member can create repository here
https://selfserve.apache.org/
We just need to select repo names in advance.
Sincerely,
Dmitriy Pavlov
пт, 25 окт. 2019 г. в 23:57, Denis Magda :
> Saikat, sounds great.
>
> As long as you're already driving this initiative, could you please
Saikat, sounds great.
As long as you're already driving this initiative, could you please check
with ASF Infra how to put this approach in place? Will we be able to create
several additional repositories for extensions and release them as part of
the Ignite project?
-
Denis
On Thu, Oct 24,
Hi Denis,
Yes, I see it now as I think more about it, I like option - 0. I am
thinking from a new member and a contributor perspective for Ignite
project, I would very much like my PR and proposal to be accepted within
Ignite community.
Regards,
Saikat
On Thu, Oct 24, 2019 at 1:56 PM Denis
Exactly, Dmitry found the right word for the reason why option-0 might be
the best one - to avoid the Ignite community *split*. All those who will be
contributing to integrations and extensions need to be able to earn a
status of an Ignite committer and PMC members. Otherwise, I'm not sure if
I agree with option 0 now, we could start from that option, and later
migrate to the Bahir Community, if it is required.
чт, 24 окт. 2019 г., 9:04 Dmitriy Pavlov :
> Hah, IMHO, it is a story of how pushing others to place their contribution
> outside ASF could lead projects to split their
Hah, IMHO, it is a story of how pushing others to place their contribution
outside ASF could lead projects to split their communities.
I believe, the Ignite community is more open and flexible in that regard.
So Option-0. is also OK from my perspective.
чт, 24 окт. 2019 г. в 04:01, Saikat Maitra
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/
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
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,
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
Also, dear Saikat Maitra, could you please describe how you see the release
cycles in Bahir Ignite Extensions and how it be related to Ignite release,
2.9, 3.0 for example.
Thank you for your energy
ср, 23 окт. 2019 г., 8:10 Alexey Zinoviev :
> Please, give me permissions too, I'd glad to help
Please, give me permissions too, I'd glad to help with this modules
migration and support part of them in future, but also we need not only
contributor but a few Committer permissions to merge In repository in other
side it could be very long proccess.
Could you ask Bahir Community about that?
Hi,
I discussed with Apache Bahir community and they are interested to have
Apache Ignite extensions as part of Apache Bahir project.
I have also requested for contributor access in Jira for Apache Bahir
project so that I can create issues and assign to myself. I can help with
code reviews as
Hello,
We wanted to discuss on a proposal to move and support the Apache Ignite
integrations as separate Ignite Extensions as discussed here
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Pub-Sub-Streamer-Implementation-td43944.html
.
The reason we wanted to move our Apache Ignite
37 matches
Mail list logo
