ous about the "user" aspect of the feature, which is generally a good
> thing.
>
> -Artem
>
> On Tue, Mar 17, 2020 at 11:59 PM Denis Magda wrote:
>
> > Hi Pavel,
> >
> > We're thinking about the same in regards to the future of Ignite
> > documentation :)
Igniters,
As long as 2.8.1 is inevitable and we already keep adding critical issues
to the working queue, let's settle on the release time frames and decide
who will be a release manager. This is the time proposed by Maxim and,
personally, I concur with such a schedule:
- Scope Freeze: April
Hello Yaroslav, welcome to the community!
I've added you to the contributors' list. Let us know if you have any
questions related to the selected task.
-
Denis
On Wed, Mar 18, 2020 at 6:03 AM Yaroslav Molochkov
wrote:
> Hello, I'm new to Ignite and I would like to join apache ignite
>
effective documentation for your open-source
projec <https://opensource.com/article/20/3/documentation>t article that I
found in one of my newsletters today. It feels like it can be used as a
reference by Igniters on some best practices.
Denis Magda
On Tue, Mar 17, 2020 at 1:03 PM Pavel Tu
Hi Nikolay,
I think that your proposal is reasonable. Agree, that all exceptions need
to be signaled properly - either with an ERROR message or by failing an
operation initiated by Visor CMD (you can return some error code and the
tool needs to process it properly). It's up to you and other Visor
cumentation writing could spotlight
> such things).
>
> On Thu, Mar 12, 2020 at 7:49 PM Denis Magda wrote:
> >
> > Igniters,
> >
> > With the final 2.8 release steps checked out today by announcing the
> > version globally (congrats!), it's a proper time to conside
Hi Aleksei,
Thanks for driving the resolution of the ticket. As I see @Taras Ledkov
and @Andrey Mashenkov has
already stepped in as reviewers and I believe they will look at your
changes soon.
-
Denis
On Mon, Mar 16, 2020 at 3:48 AM Aleksei Litsov
wrote:
> Hello Igniters!
>
> I send PR for
support query cancel
> >>>
> >>> 7.JDBC:Added support query timeout
> >>>
> >>> 8.REST:Added "caches" param for "top" command
> >>>
> >>> 9.REST:Added baseline topology commands to REST API
> >>&
Mauricio
>
>
>
>
> On Fri, Mar 13, 2020 at 1:23 PM Denis Magda wrote:
>
>> Mauricio,
>>
>> I've just spotted that all 2.8 API files (java, .net, etc.) miss the GA
>> breadcrumbs. Most likely, this step of our release process was not fully
>> co
Hello Veena,
Our moderators' queue for the Ignite dev list is flooded with your emails.
As suggested earlier, please subscribe to the dev list first and that will
eliminate the need for all further moderation of your messages:
https://ignite.apache.org/community/resources.html#mail-lists
Also,
Mauricio,
I've just spotted that all 2.8 API files (java, .net, etc.) miss the GA
breadcrumbs. Most likely, this step of our release process was not fully
completed:
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-6.3.5.Updatereferencetodocsfromsite,SEOupdates
Igniters,
With the final 2.8 release steps checked out today by announcing the
version globally (congrats!), it's a proper time to consider and tweak our
release process, making completion of some phases more predictable and
aligned. I would like to dedicate this thread solely to changes related
Nikolay,
That's an excellent idea. As Kseniya mentioned, there is plenty of tools
for such events - gotomeeting/webinar, zoom, etc. I have not heard that ASF
guides using any, it's up to us.
Also, I'll be doing a generic webinar about 2.8 (check this discussion [1])
featuring the new metrics
Folks,
Not sure that we will be moving in the right direction discussing dates
with no clarity of what is to be released in a specific version. Instead,
let's talk out our plans/tasks first and then put them on a timeline. That
certainly applies to big releases such as 2.9 that deserve a
list, please open a ticket for INFRA.
-
Denis
On Wed, Mar 11, 2020 at 2:42 PM Ivan Pavlukhin wrote:
> Denis,
>
> By the way. Do you know who else receives messages for moderation (I do
> not)?
>
> Best regards,
> Ivan Pavlukhin
>
> ср, 11 мар. 2020 г. в 19:05, Denis
is, Folks,
>
> It the link correct?
> https://blogs.apache.org/ignite/entry/ignite-2-8-released-less
>
> I can't get access to it. Can anyone else confirm that everything is OK?
>
> On Wed, 11 Mar 2020 at 23:52, Denis Magda wrote:
> >
> > Folks,
> >
> > I've publis
once they will be
> rebalanced.
> This leads to subsequent LAA PME (after Left switch).
> Initial PME is required to calculate and apply new affinity and perform
> preparations for LAA.
>
> On Tue, Mar 10, 2020 at 7:25 PM Denis Magda wrote:
>
> > Anton,
> >
> >
On Wed, Mar 11, 2020 at 9:33 AM Artem Budnikov
wrote:
> Denis,
>
> I'm waiting for answers from Alexey. I can't really tell how lont it will
> take. Of couse, we can publish everything right now and improve some pages
> later.
>
> -Artem
>
> On Wed, Mar 11, 2020 at
Aleksey, welcome to the community!
For some reason, your personal address is a bit clumsy
"aleksei_lit...@epam.com.invalid". Is it some issue with the EPAM email
domain?
-
Denis
On Wed, Mar 11, 2020 at 2:04 AM Aleksei Litsov
wrote:
> Thank you very much!
>
>
> -Original Message-
>
t; > >> wrote:
> >>> > >>> Guys,
> >>> > >>>
> >>> > >>> I see that there is already version 2.8 for Ignite docs on
> readme.io.
> >>> > >>> Who created it and when? I've c
Hi,
Please subscribe to the dev mailing list so that we don't need to moderate
and approve your emails.
https://ignite.apache.org/community/resources.html#mail-lists
Also, it looks like this question is more suited for the user list. Please
send it there (don't forget to subscribe on the user if
@Nikolay Izhikov , @Andrey Gura ,
could you folks check out this thread?
I have a feeling that what Dominik is describing was talked out before and
rather some sort of a limitation than an issue with the current
implementation.
-
Denis
On Tue, Mar 3, 2020 at 11:41 PM Dominik Przybysz
wrote:
gt;
> Sincerely,
> Dmitriy Pavlov
>
> сб, 7 мар. 2020 г. в 01:08, Denis Magda :
>
> > Dmitry,
> >
> > Agree on the Github repository. Let me look into it. If you have any
> > pointers or came across any instructions earlier please let me know.
> >
>
nis,
>
> >> the blocking PME no longer happens if a node leaves the cluster
> We should mention this should be the baseline node
>
> On Tue, Mar 10, 2020 at 9:40 AM Denis Magda wrote:
>
> > Pavel, thank you. I referred to your article from a blog post to be
> > publishe
:
> Published: https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.8/
>
> On Sat, Mar 7, 2020 at 1:49 AM Pavel Tupitsyn
> wrote:
>
> > Denis, ok, I'll publish on Monday afternoon then (UTC), weekend is not
> the
> > best time.
> >
> > Thanks,
> > Pavel
&g
Mike,
Have we filed a ticket to fix the issue in an upcoming release?
On Monday, March 9, 2020, Mikhail wrote:
> Hi Dominik,
>
> in new zookeeper 3.5.5 version part of classes were moved in new jar:
> https://mvnrepository.com/artifact/org.apache.zookeeper/
> zookeeper-jute/3.5.5
> which is
e [2].
> In 2.8 we have refined build-related things (jar file handling), and made
> sure that recent .NET versions are supported.
>
> [1]
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients
> [2] https://habr.com/ru/comp
Alex, thanks for monitoring various discussion threads and sharing these
problems with the rest of the dev community.
>> As a short-term solution for [2] I suggest to force reads from a primary
> node inside optimistic serializable transactions.
Totally agree on this. Anyway, consistency and
we need to work on better
> > content (home page specifically).
> > Thanks!
> > --
> > Nikita Ivanov
> >
> >
> >
> > On Thu, Mar 5, 2020 at 3:18 PM Denis Magda wrote:
> >
> > > Folks,
> > >
> > > As many of you know,
Folks,
Does it make sense to take an approach of Python ML implementation
available for GridGain in a beta mode? (where Python APIs wrap around Java
ML library)
https://www.gridgain.com/docs/latest/developers-guide/python-ml/using-python-ml
-
Denis
On Thu, Mar 5, 2020 at 6:50 AM Alexey
avel Tupitsyn wrote:
> Denis,
>
> The first post is going to be ready soon, probably by tomorrow.
> Here is a draft, feedback welcome:
>
> https://github.com/ptupitsyn/ptupitsyn.github.io/blob/ignite-2.8/_posts/2020-03-05-Whats-New-In-Ignite-Net-2.8.md
>
> On Wed, Mar 4, 2020 a
Folks,
As many of you know, these days I mostly contribute by optimizing our
website, preparing different content including documentation/articles, and
presenting the project at various events. One of the continuous website
activities we undertake together with Mauricio and Ignacio is search
, Mar 5, 2020 at 12:27 PM Denis Magda wrote:
> Ilya,
>
> Thanks for driving this activity. It would be nice to shift this
> conversation to another thread, agree on the slim package structure and
> release it for 2.8. This discussion is not the most visible one for the
> to
out announcing. We've got some questions\bugs
> on
> > > > >>> user-list already [1] [2].
> > > > >>>
> > > > >>>
> > > > >>> [1]
> > > > >>>
> > http://apache-ignite-users.70518.x6
nion it is not correct to consider
> release in progress.
>
> Agree that 2.8.1 sounds as a proper option here.
>
> [1] https://mvnrepository.com/artifact/org.apache.ignite/ignite-core/2.8.0
>
> Best regards,
> Ivan Pavlukhin
>
> ср, 4 мар. 2020 г. в 17:08, Denis Magda :
&
Hi Igniters,
Let me introduce you to Mike James, who has been working on a gripping
project that uses Apache Ignite as a backbone for a distributed DMX Control
system. That's a use case of the entertainment industry and, hopefully,
many rockstars will switch to the solution to produce light
ot;
> >>
> >> The three other features are limitations that were present in Ignite
> >> 2.7 and now they are removed. Since they were never mentioned in the
> >> docs, there is nothing to do.
> >>
> >> -Artem
> >>
&
o you think? Should we have a schedule of some sorts?
>
> On Tue, Mar 3, 2020 at 9:58 PM Alexey Zinoviev
> wrote:
>
> > Sounds ineresting, will help with the post, please share the template,
> not
> > sure about webinar
> >
> > вт, 3 мар. 2020 г., 20:59 Deni
.1.
> > >
> > > [1] https://ignite.apache.org/download.cgi
> > > [2] https://mvnrepository.com/artifact/org.apache.ignite
> > >
> > >
> > > On Wed, Mar 4, 2020 at 10:06 AM Nikolay Izhikov
> > wrote:
> > >
> > >> Hel
emoved:
>
>
> Added support best effort affinity for thin clients (partition awareness)
>
> Java thin client does not support partition awareness. Nodejs and python
> thin clients from the distribution package do not have signs of this
> feature as well.
>
> Igor,
>
> Coul
Hello Prachi,
A recommended approach is to deploy Ignite in its standard configuration
and pre-load the required data there. This page shares more details:
https://www.gridgain.com/docs/latest/integrations/datalake-accelerator/getting-started
In case synchronization is needed between Ignite and
Ilya,
Thanks for catching that and sharing. I wonder if there are any other
blockers that were pushed to 2.8.x version. If there are a few then we can
produce 2.8.1 shortly, otherwise, it sounds reasonable to me to fix the
issue with putAll, update the binaries and finish the process.
-
Denis
Could we also update the "Overview" page with the content from the README
file of GitHub?
https://github.com/apache/ignite/blob/master/README.md
-
Denis
On Tue, Mar 3, 2020 at 1:26 PM Maxim Muzafarov wrote:
> Igniters,
>
>
> I've just found that a script with docked Apache Ignite on docker
Igniters,
Let's discuss approaches for a global announcement/promotion of the
release. I would suggest focusing on a blog post and a community webinar.
The blog post will introduce significant improvements (service grid, thin
clients, new metrics system, ML, etc.) sharing references to
Emmanouil, thanks, I've reviewed and merged the changes!
-
Denis
On Sun, Mar 1, 2020 at 4:30 PM ReadMe wrote:
> *Emmanouil Gkatziouras* suggested edits to page *Amazon AWS Discovery*.
>
> +++ Added: 27
>
> --- Removed: 2
>
> *Added ALB documentation.*
>
> Documentation for the new Ignite ALB
/project/apacheignite/v2.7.6/docs/gradient-boosting
>
>12.
>https://dash.readme.io/project/apacheignite/v2.7.6/docs/model-updating
>13.
>
> https://dash.readme.io/project/apacheignite/v2.7.6/docs/ann-approximate-nearest-neighbor
>
>
>
>
> ср, 26 февр. 2
Maxim,
Please stay in touch with Artem If you'd like to release Ignite 2.8 docs.
It's a bit complicated with readme and either Artem can complete this step
or he can collaborate with you letting you experience it. Anyway, before we
release 2.8 version of the docs we need to finish the pages. Here
gt; > need some time for documentation preparation.
> >
> > On Mon, 2 Mar 2020 at 18:40, Denis Magda wrote:
> >>
> >> Hi Maxim,
> >>
> >> This sounds like an option but can take delay the release for more than
> a
> >> week. Alte
Alex Schrbakov,
As a reviewer, could you merge the changes?
-
Denis
On Mon, Mar 2, 2020 at 6:15 AM Zhenya Stanilovsky
wrote:
>
> Hello, no objections found, plz who can merge it [1]?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12725
>
>
>
Hi Maxim,
This sounds like an option but can take delay the release for more than a
week. Alternatively, someone from the PMC group can execute this step for
you. Is there anybody who can do that?
-
Denis
On Mon, Mar 2, 2020 at 6:21 AM Maxim Muzafarov wrote:
> Ignite PMCs,
>
>
> Hopefully,
QL
> query will not see the value anymore. So, the same inconsistency will
> appear.
>
> Best regards,
> Ivan Pavlukhin
>
> пт, 28 февр. 2020 г. в 13:23, Prasad Bhalerao <
> prasadbhalerao1...@gmail.com>:
> >
> > Can someone please comment on this
> ignite-twitter
> ignite-web
> ignite-yarn
> ignite-zeromq
> ignite-zookeeper
>
> Plus, remove benchmarks/ from slim package either.
>
> WDYT?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 28 февр. 2020 г. в 19:57, Denis Magda :
>
> >
Maxim,
Finally, thanks a lot for starting the voting process!
I've already cast my vote and want to bring up some issues that are not
blockers though:
1. Ignite technical documentation is not finished yet - @Artem Budnikov
is coordinating this process as well as
contributes to many
+1 (binding)
Downloaded, started a cluster, ran several examples pulling Maven
artifacts from the staging.
-
Denis
On Fri, Feb 28, 2020 at 7:09 AM Maxim Muzafarov wrote:
> Dear Community,
>
>
> I have uploaded a release candidate to:
>
Duplicate message, responded in a similar thread.
-
Denis
On Wed, Feb 26, 2020 at 8:04 AM Javad Alimohammadi <
bs.alimohamm...@gmail.com> wrote:
> Hello to everybody. I would be glad to be part of your community.
>
> *My Areas of Expertise *
> Core Java, Concurrent Programming, Performance
Hello Javad,
Welcome to the community, and thanks for sharing your areas of expertise
with interests! You were added to the contributors' list in JIRA.
Please check the "Pick a Ticket" section on this page [1] selecting a task
you'd like to start with. Our community members have refreshed the
Igor Sapego, Igniters,
I've been working on Ignite website improvements that will be introduced
and contributed later and found that we still don't generate API references
for Node.JS, PHP, Python. The APIs are not even shipped withing binary
packages.
Do our scripts for build/release generate
Ignite Dev team,
This sounds like an issue in our replicated cache implementation rather
than an expected behavior. Especially, if partitioned caches don't have
such a specificity.
Who can explain why write-through needs to be enabled for replicated caches
to reload an entry from an underlying
post in this thread a few examples of the documentation
> > tickets in JIRA for the current release, to create them correctly?
> >
> > пн, 24 февр. 2020 г. в 14:53, Alexey Zinoviev :
> >
> > > Ok, will make ticket, no problemo
> > >
> > >
> component.
>> After some consultation and review from Artem side I'll add new
>> documentation on readme.io.
>>
>>
>>
>> чт, 20 февр. 2020 г. в 02:34, Denis Magda :
>>
>>> Artem,
>>>
>>> Thanks for stepping in and preparing the l
t; >
> > Sure, I'll take a look at the code shortly.
> >
> > --
> > Thank you,
> > Sergey.
> >
> > On Mon, Jan 27, 2020 at 8:59 PM Denis Magda wrote:
> >
> > > I support the idea of triggering such tests on demand. We can create a
> > wiki
> >
Hi Ilya,
We can oblige users to implement Comparable if they use BinaryObject keys.
Ignite can print out a warning if BinaryObject keys passed to putAll
methods don't do that.
I also wonder how a similar task was solved for Ignite INSERTs. Our engine
should use BinaryObjects for compound primary
Folks,
Is there anything else apart from the open documentation tickets that
prevent us from starting the release vote? I think that it should take
around two weeks to run the release through the vote and announce it. The
top doc changes should be finished throughout that time already.
-
Denis
Artem,
Thanks for stepping in and preparing the list of top priority documentation
tasks! How about labeling those tickets somehow and creating a filter
similar to this one [1] but for "Required & Unresolved Documentation
Tasks"? I would simply add this as a new section to the Ignite 2.8 release
Peter,
Would you mind checking this issue and suggest a proper solution?
Dmitry,
Might this be somehow related to the RPM changes ASF INFRA suggested to
make?
-
Denis
On Wed, Feb 19, 2020 at 4:33 AM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:
> As seen in the user mailing
lly, I've already filtered documentation issues previously and
> left only major documentation tasks. Should I shrink the list more?
>
> On Thu, 13 Feb 2020 at 18:58, Denis Magda wrote:
> >
> > Maxim,
> >
> > Thanks for the list. How many of those tickets relate t
e2.8-Unresolveddocumentationtasks
> [2] https://issues.apache.org/jira/browse/IGNITE-12408
>
> On Thu, 13 Feb 2020 at 00:48, Denis Magda wrote:
> >
> > Hi Maxim,
> >
> > Do you have any understanding in regards to documentation readiness? I do
> > reme
Hi Maxim,
Do you have any understanding in regards to documentation readiness? I do
remember Nikolay was creating a page for the new metrics framework and
Artem stepped in as a reviewer. But not sure if that supposedly the largest
item is completed and if the other pages need to be updated.
-
[-1 Prohibit]
-
Denis
On Mon, Feb 10, 2020 at 12:02 AM Alexey Goncharuk
wrote:
> Dear Apache Ignite community,
>
> We would like to conduct a formal vote on the subject of whether to allow
> or prohibit a joint existence of @deprecated annotation for an old API
> and @IgniteExperimental [1]
Hello Mahesh,
Welcome to the community! It's a pleasure to get you interested in the
contribution.
Just in case, copying some useful pages for getting started:
- Ignite contribution process and a collection of tickets for newcomers:
https://ignite.apache.org/community/contribute.html
-
Hello Erel,
Thanks for introducing yourself and welcome to the community! Hope Ignite
will work out for your solutions, and the community will benefit by having
you as a member. Don't hesitate to reach out for architectural discussions
or if you come across any uncertainties.
Most likely, you've
t; >>> practice earlier because it seems that we need to release a Flink
> > >>> integration soon because Ignite 2.8 is going to be released without
> > >>> that integration bundled.
> > >>>
> > >>> As usual we need to decide about versioni
The justification and choices look crystal clear to me.
-
Denis
On Wed, Feb 5, 2020 at 1:36 PM Alexey Goncharuk
wrote:
> Igniters,
>
> We would like to add some formal requirements to the API deprecation
> process. So far the API deprecation was more like intuitive-driven which
> recently led
ata-on-deactivate was disabled by default? There
> should be a reason for that. Any data consistency issues when node gets
> activated anew? We may use both solutions because the flag can be switched
> off again.
>
> ср, 5 февр. 2020 г. в 20:47, Denis Magda :
>
> > Hi Vladimir,
>
ORY_ON_DEACTIVATE
>
> [2] https://issues.apache.org/jira/browse/IGNITE-12614
>
>
> вт, 4 февр. 2020 г. в 22:45, Denis Magda :
>
> > That's the best solution for this scenario. Should we readjust the
> already
> > created ticket [1] suggesting to implement the
Alex, did you have a chance to review Saikat’s changes related to the
extensions repository organization and release approach?
Denis
On Wednesday, February 5, 2020, Nikolay Izhikov wrote:
> Hello, Igniters.
>
> We don't have a release process for newly created ignite-extensions
> modules.
> I
Let's run a vote if that's the only option to come to a consensus. It will
be best if either Alex Goncharuk, Andrey Gura or Nikolay Izhikov creates a
discussion thread stating the problem and possible choices. Folks, who
would like to take over?
Generally, the vote should help us to decide how to
ppen if a partition is lost in
> > inactive state? What if such node joins back the cluster after? Etc.
> >
> > пт, 31 янв. 2020 г. в 20:57, Denis Magda :
> >
> > > Back up Ivan's opinion here. Initially, the activation/deactivation was
> > > created for the
+1 from my end. It doesn't sound like a big deal if Ignite users need to
define separate groups for atomic and transactional caches.
-
Denis
On Tue, Feb 4, 2020 at 3:28 AM Ivan Rakov wrote:
> Igniters,
>
> Apparently it's possible in Ignite to configure a cache group with both
> ATOMIC and
Hi Kartheek,
Welcome to the community! It's nice to see you got interested in the
project and decided to contribute.
Please check this page out for commonly asked questions pertaining to the
contribution process as well as a list of tickets for newcomers:
Alex Scherbakof, as the one who created the ticket, could you please help
Artem and share more details?
-
Denis
On Fri, Jan 31, 2020 at 4:54 AM Artem Demchenko
wrote:
> Hi, everyone! I have a question about the following task:
> https://issues.apache.org/jira/browse/IGNITE-11663.
>
> The
gt; Because originally the sole purpose of deactivation was resource
> > deallocation.
> >
> > чт, 30 янв. 2020 г. в 22:13, Denis Magda :
> >
> > > Such a revelation for me that data is purged from RAM if someone
> > > deactivates the cluster
Forwarding this thread to the dev list.
Ignite SQL experts, could you check this thread and create a proper ticket
for this minor usability improvement? Probably, the ticket is not even
needed.
Basically, our driver reports this error - *SQLException: Client is
invalid. Probably cache name is
Such a revelation for me that data is purged from RAM if someone
deactivates the cluster. Alex, do you remember why we decided to implement
it this way initially?
-
Denis
On Thu, Jan 30, 2020 at 2:09 AM Alexey Goncharuk
wrote:
> I agree on CLI and JMX because those interfaces can be used by a
Nikolay, Andrey,
Would you be the best committers to help out here? You are already deeply
involved in metrics development and can quickly suggest Lev how to proceed
with this task.
-
Denis
On Thu, Jan 30, 2020 at 2:46 AM Лев Киселев
wrote:
> Hello everyone, I have question about following
Folks, seriously, we should deprecate an existing API only after the new
one is no longer considered experimental. There might be API and
configuration changes in the experimental API before it's announced as GA.
I would encourage us to do this properly - let's release the new APIs
labeling them
Folks, why don't you name the channel "ignite-spring-framework_russian" in
Slack ;)
-
Denis
On Wed, Jan 29, 2020 at 12:50 AM Maksim Stepachev <
maksim.stepac...@gmail.com> wrote:
> Yes, I do.
>
> ср, 29 янв. 2020 г. в 11:22, Sergey Chernolyas <
> sergey.chernol...@gmail.com
> >:
>
> > Do you
Hi Sergey, welcome back!
The dev list is a preferable way for communication. It's ok to keep the dev
list in CC all the times even if Maksim will be working mostly with you on
the Spring Data tasks.
Anyway, you can use our community Slack channel for instant messaging:
Igniters,
I've just published an article that describes one of the reasons for why an
Ignite cluster can underperform. It's reviewed how a selection of proper
Ignite APIs can put less pressure on the network and proliferate the
performance:
Igor, thanks for being an invaluable member of the community all this time!
Congrats!
-
Denis
On Sun, Jan 26, 2020 at 9:58 PM Ivan Pavlukhin wrote:
> Hello Ignite Community,
>
> The Project Management Committee (PMC) for Apache Ignite has invited
> Igor Sapego to join the PMC as a new member
Folks,
We had this discussion about communication channels before and summarized
it on this wiki:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Collaborate
Dev list is a preferred channel but we're free to go to Slack or Telegram
(mention it there if you'd like) on some occasions.
-
gt; > > > > > I also think we should keep both .Net and C++. .Net is runnable
> out
> > > of
> > > > > box
> > > > > > which is awesome, and C++ needs building but it is rather small
> in
> > > > source
> > > >
azon.com/blogs/opensource/aws-promotional-credits-open-source-projects/
> > >
> > > King Regards
> > > *Emmanouil Gkatziouras*
> > > https://egkatzioura.com/ |
> > > https://www.linkedin.com/in/gkatziourasemmanouil/
> > > https://gi
Sergey,
Thanks for a compact and clear article. I especially enjoyed the part that
explains how to connect from a local laptop to an already running Ignite
cluster on AWS. Looking forward to more content from you!
-
Denis
On Wed, Jan 22, 2020 at 11:35 PM Sergey Chugunov
wrote:
> Hello
Hi Luis,
Presently, the community is on the route of Ignite simplification. We're
trying to define Ignite core that has minimal dependencies with 3rd party
libraries. That also led to the modularization initiative [1] with the
first results in the form of Ignite Extensions repository where we're
to submit? It can be a deep-dive about Ignite internals
or Ignite use case overview. We can co-present. Also, GridGain is ready to
sponsor your trip if the talk is accepted.
-
Denis
On Tue, Jan 21, 2020 at 5:22 PM Denis Magda wrote:
> Ignite folks, just bringing to your attention and encour
jira/browse/IGNITE-12398
> [3] https://github.com/gkatzioura/ignite-aws-deploy
>
> Kind regards,
> *Emmanouil Gkatziouras*
> https://egkatzioura.com/ |
> https://www.linkedin.com/in/gkatziourasemmanouil/
> https://github.com/gkatzioura
>
>
> On Tue, 14 Jan 20
Igniters,
Just a reminder for those who live in the San Francisco Bay Area. We're
meeting tomorrow at Azul HQ.
-
Denis
On Thu, Jan 9, 2020 at 12:01 PM Denis Magda wrote:
> Igniters,
>
> Some of you should have come across an article by Simon Ritter describing
> how Ignite and A
Ignite folks, just bringing to your attention and encourage anybody
interested to submit an Ignite-related session. Both Alex Zinoviev and I
presented at ApacheCons the previous year -- the events are worth attending
and speaking at.
-
Denis
-- Forwarded message -
From: Rich
Folks, if you don't mind I'll share some thoughts/suggestions as an
observer who was not involved in the feature development.
It's absolutely 'ok' to deprecate an API that is replaced with a much
better version. However, we should do this only when the new APIs are
production-ready. If there are
401 - 500 of 3093 matches
Mail list logo
