Pavel,
Thank you for starting this discussion!
Controlling all this repo options on our side sounds very attractive.
Personally I do not have any arguments about the proposal.
Best regards,
Ivan Pavlukhin
чт, 7 мая 2020 г. в 17:39, Pavel Pereslegin :
>
> Igniters,
>
> recent github pull
Hi Dmitry, thanks!
Please add the following to the project activity section:
- Released a new version of the Apache Ignite website:
https://ignite.apache.org
- Prepared a public roadmap with significant improvements planned for
the rest of 2020:
Maxim, congrats!
Great job, respect!
чт, 7 мая 2020 г. в 23:04, Vyacheslav Daradur :
> Great job! My congratulations!
>
> чт, 7 мая 2020 г. в 16:09, Alex Plehanov :
>
> > Maxim, congratulations!
> >
> >
> > чт, 7 мая 2020 г. в 15:12, Denis Garus :
> >
> > > Maxim, Congrats!
> > > Great job!
> >
Igor Seliverstov created IGNITE-12991:
-
Summary: Calcite integration. Pass cancel flag to VolcanoPlanner
Key: IGNITE-12991
URL: https://issues.apache.org/jira/browse/IGNITE-12991
Project: Ignite
Great job! My congratulations!
чт, 7 мая 2020 г. в 16:09, Alex Plehanov :
> Maxim, congratulations!
>
>
> чт, 7 мая 2020 г. в 15:12, Denis Garus :
>
> > Maxim, Congrats!
> > Great job!
> >
> > чт, 7 мая 2020 г. в 15:02, Nikita Amelchev :
> >
> > > Maxim, congrats!
> > >
> > > чт, 7 мая 2020 г. в
Igniters,
Thanks for helping to put together our first roadmap for the rest of 2020
[1]. Turned out to be a handy source that should be appreciated by Ignite
application developers.
By looking at the page, it feels like we can plan a couple of releases:
- Ignite 2.9 (early September) - it
Ivan,
This is the default configuration of travis-ci. Nothing was changed by me here.
Please, correct me if I'm wrong. According to my knowledge the option
mentioned by you have the following meaning:
- check `continuous-integration/travis-ci/pr` -- travis will merge
changes to the master
Folks,
I've updated the checklist according to your suggestions [1].
Added.
+ Treat PR title as the final squashed commit message.
+ The description explains what and why vs. how
Removed.
- Commits have the following pattern
[1] https://github.com/apache/ignite/pull/7765/files
On Mon, 4 May
IMO, we can remove. This badge does not work since GitHub started to
cache images. Now TC's status .SVG does not work properly.
чт, 7 мая 2020 г. в 09:25, Ivan Pavlukhin :
> Folks,
>
> I created a ticket [1] and prepared PR with magic number =).
>
> Please review.
>
> [1]
Igniters, the feature is ready for review:
https://issues.apache.org/jira/browse/IGNITE-12932
https://github.com/apache/ignite/pull/7744
On Thu, May 7, 2020 at 6:23 PM Pavel Tupitsyn wrote:
> Alex,
>
> Event subscription is a good idea. We should certainly add this in future.
> However, it
Alex,
Event subscription is a good idea. We should certainly add this in future.
However, it might be non-trivial with multiple connections: should we
subscribe on every server?
Then we'll get an event from every server, which seems redundant.
Igor,
Agreed. Let's keep existing behavior.
On
The Apache Ignite Community is pleased to announce the release of
Apache Ignite Spring Boot extensions 1.0.0
Apache Ignite [1] is a memory-centric distributed database, caching,
and processing platform for transactional, analytical, and streaming
workloads delivering in-memory speeds at petabyte
Hi Igniters,
To increase involvement of each member of the community and increase
transparency I'd like to share report draft for ASF board with all dev@
community. Thanks to Ivan P. for this idea.
What would you like to add to this report? Major features, events, popular
publications could be
Igniters,
recent github pull requests are not automatically linked to the jira
tickets.
Infra advises creating a yaml configuration in the root of the repository
with the settings for the github bot [1].
Examples of such configuration in Hive [2] and HBase [3].
I suggest the following settings
Pavel,
First of all, I think we need to move it out of scope of this feature.
Also, why do we need to keep connection alive? I think, if user do not
use connection for a long time and connection is lost we could just
detect this and re-establish connection on the next user action which
requires
Done.
> 7 мая 2020 г., в 13:20, Denis Garus написал(а):
>
> Nikolay,
> could we add the simple improvement [1] to 2.8.1 scope?
>
> 1. https://issues.apache.org/jira/browse/IGNITE-12983
>
> чт, 30 апр. 2020 г. в 11:26, Alex Plehanov :
>
>> Nikolay,
>>
>> TC results: [1], [2]
>> I've
Maxim, congratulations!
чт, 7 мая 2020 г. в 15:12, Denis Garus :
> Maxim, Congrats!
> Great job!
>
> чт, 7 мая 2020 г. в 15:02, Nikita Amelchev :
>
> > Maxim, congrats!
> >
> > чт, 7 мая 2020 г. в 14:55, Nikolay Izhikov :
> > >
> > > Congrats.
> > >
> > > > 7 мая 2020 г., в 14:54, Ivan
Hi, that's it.
06.05.2020, 19:50, "Ivan Rakov" :
> Hi,
>
> IGNITE_WRITE_REBALANCE_PARTITION_DISTRIBUTION_THRESHOLD - threshold
>> duration rebalance of cache group after which partitions distribution is
>> output, set in milliseconds, default value is 10 minutes.
>
> Does it mean that if the
Maxim, Congrats!
Great job!
чт, 7 мая 2020 г. в 15:02, Nikita Amelchev :
> Maxim, congrats!
>
> чт, 7 мая 2020 г. в 14:55, Nikolay Izhikov :
> >
> > Congrats.
> >
> > > 7 мая 2020 г., в 14:54, Ivan Pavlukhin
> написал(а):
> > >
> > > Maxim,
> > >
> > > My congratulations! Well deserved!
> > >
>
Maxim, congrats!
чт, 7 мая 2020 г. в 14:55, Nikolay Izhikov :
>
> Congrats.
>
> > 7 мая 2020 г., в 14:54, Ivan Pavlukhin написал(а):
> >
> > Maxim,
> >
> > My congratulations! Well deserved!
> >
> > P.S. We should mention snapshots for persistent caches in the
> > achievement list. Great job!
>
Congrats.
> 7 мая 2020 г., в 14:54, Ivan Pavlukhin написал(а):
>
> Maxim,
>
> My congratulations! Well deserved!
>
> P.S. We should mention snapshots for persistent caches in the
> achievement list. Great job!
>
> Best regards,
> Ivan Pavlukhin
>
> чт, 7 мая 2020 г. в 14:47, Dmitriy Pavlov
Maxim,
My congratulations! Well deserved!
P.S. We should mention snapshots for persistent caches in the
achievement list. Great job!
Best regards,
Ivan Pavlukhin
чт, 7 мая 2020 г. в 14:47, Dmitriy Pavlov :
>
> The Project Management Committee (PMC) for Apache Ignite
>
> has invited Maxim
Hi Igniters,
Only whole project may go to the attic. Main reason of moving project to
the attic is inactive community and less than 3 PMC members voting for new
release.
So attic is more about waiting for new community to resurrect project, and
less about codebase.
I suggest us, as always,
The Project Management Committee (PMC) for Apache Ignite
has invited Maxim Muzafarov to become new PMC member and we are pleased to
announce that he has accepted.
Maxim is active dev list participant, speaker at meetups, and contributes
to additional checks of the product using travis and
Alexey Goncharuk created IGNITE-12990:
-
Summary: Remove static thread group from IgniteSpiThread
Key: IGNITE-12990
URL: https://issues.apache.org/jira/browse/IGNITE-12990
Project: Ignite
Anton Vinogradov created IGNITE-12989:
-
Summary: Tx recovery should log statuses to TimeBag
Key: IGNITE-12989
URL: https://issues.apache.org/jira/browse/IGNITE-12989
Project: Ignite
Bastien Durel created IGNITE-12988:
--
Summary: c++ thin client installer misses some headers
Key: IGNITE-12988
URL: https://issues.apache.org/jira/browse/IGNITE-12988
Project: Ignite
Issue
Nikolay,
could we add the simple improvement [1] to 2.8.1 scope?
1. https://issues.apache.org/jira/browse/IGNITE-12983
чт, 30 апр. 2020 г. в 11:26, Alex Plehanov :
> Nikolay,
>
> TC results: [1], [2]
> I've cherry-picked IGNITE-12933 and IGNITE-12855 to 2.8.1
>
> [1]:
>
>
Hello!
I think we should move it to a separate repository, but not Attic.
I can see the scenario where there would be recurrence of interest to this
tool and somebody may step in to update it.
Regards,
--
Ilya Kasnacheev
ср, 6 мая 2020 г. в 22:20, Denis Magda :
> Folks,
>
> Personally, I
Hello!
I think it is OK if client loses cluster, in this case it should only check
the addresses with which it was configured to start.
Regards,
--
Ilya Kasnacheev
ср, 6 мая 2020 г. в 17:31, Pavel Tupitsyn :
> Igniters, let's discuss the following issue:
>
> For partition awareness, and now
Yes, it will work this way.
чт, 7 мая 2020 г. в 10:43, Anton Vinogradov :
> Seems I got the vision, thanks.
> There should be only 2 ways to reset lost partition: to gain an owner from
> resurrected first or to remove ex-owner from baseline (partition will be
> rearranged).
> And we should make
Seems I got the vision, thanks.
There should be only 2 ways to reset lost partition: to gain an owner from
resurrected first or to remove ex-owner from baseline (partition will be
rearranged).
And we should make a decision for every lost partition before calling the
reset.
On Wed, May 6, 2020 at
Folks,
I created a ticket [1] and prepared PR with magic number =).
Please review.
[1] https://issues.apache.org/jira/browse/IGNITE-12987
Best regards,
Ivan Pavlukhin
пн, 4 мая 2020 г. в 10:01, Ivan Pavlukhin :
>
> Hi Igniters,
>
> Inspired by a neighbor thread about PR checks [1]. It brought
Ivan Pavlukhin created IGNITE-12987:
---
Summary: Remove TC badge from README.md
Key: IGNITE-12987
URL: https://issues.apache.org/jira/browse/IGNITE-12987
Project: Ignite
Issue Type: Task
34 matches
Mail list logo
