I vote for a separate repo for the Ignite Abbrev Plugin project.
The reason is:
Ignite Abbrev Plugin - build on top of IntelliJ Platform SDK [1] and
can't be easily packaged without it, moreover, it doesn't depend on
Ignite internals (unlike .NET/C++ clients).
One more place where we could place
I vote for a separate repo for the TC helper project.
IMO TC Helper - is an application project and a separate repo is a
more convenient way to the project developing.
One more place where we could place the project (if the place
maintained by Ignite's commiters):
https://github.com/apacheignite
TcpDiscoveryVmIpFinder can be configured with 127.0.0.1. Example with
remote nodes will work fine on a single machine. Users rarely run examples
on multiple machines.
чт, 19 июля 2018 г. в 5:30, Dmitriy Setrakyan :
> I am confused, the TcpDiscoveryVmIpFinder will only discover nodes with
> specif
Alexander Kalinin created IGNITE-9032:
-
Summary: Remove extra dependecy from web console frontend
Key: IGNITE-9032
URL: https://issues.apache.org/jira/browse/IGNITE-9032
Project: Ignite
I
I am confused, the TcpDiscoveryVmIpFinder will only discover nodes with
specified list of IPs. Don't we have examples that require remote nodes to
join?
D.
On Wed, Jul 18, 2018 at 7:52 AM, Stanislav Lukyanov
wrote:
> > It can seem not important, but saves a minute for everyone.
> No, it actuall
Dmitriy,
I think you should file an INFRA ticket and ask if this is possible.
D.
On Wed, Jul 18, 2018 at 3:12 PM, Denis Magda wrote:
> Dmitriy,
>
> Things for clearing the things out. No objections from my side then.
>
> Let's see what other Ignite fellows think on your proposal. Someone might
Dmitriy,
Things for clearing the things out. No objections from my side then.
Let's see what other Ignite fellows think on your proposal. Someone might
have a different perspective.
--
Denis
On Wed, Jul 18, 2018 at 1:58 PM Dmitry Pavlov wrote:
> Hi Denis,
>
> It will made things simple.
>
> 1
Yes, I agree. My concern is related only to process implementation aspect,
I wonder if it is technically possible.
Generally I like idea of automatic control.
ср, 18 июл. 2018 г. в 23:21, Denis Magda :
> Hi folks,
>
> Artem's proposal might simplify and make our doc tickets tracking less
> error
Hi Denis,
This option can be considered also. I have no arguments against this
solution.
In the same time I think Ignite developer will need pre-build distributive
(Jar) of plugin, probably in /idea subfolder.
So standalone ASF repo & [build/link to build] in main repo can be still
considered. T
Currently BLT can’t be used without persistence – only persistent caches are
affected by it.
AFAIR making non-persistent caches make use of the baseline topology is the
plan for IEP-4 Phase 2.
Thanks,
Stan
From: Valentin Kulichenko
Sent: 19 июля 2018 г. 0:04
To: dev@ignite.apache.org
Subject: B
Folks,
By default baseline topology is enforced only if persistence is enabled and
is not defined in in-memory only scenario. But does this mean that I still
CAN use it without persistence?
In some cases users want to avoid rebalancing in case of a node failure
because it's assumed that this node
Hi Denis,
It will made things simple.
1) For example any comitter will be able to change rules of notification
and fix the Bot if something goes wrong. Now it is my github repo. ASF repo
will guarantee that code will be always accessible by community members.
2) Being a part of ASF repo the Bot
Hi Stan,
I have one more point that I'm trying to clarify. You mentioned that
clientFailureDetectionTimeout is ignored by client nodes. But if so, what
happens on the client side in case of network failure (i.e. if both client
and server nodes are alive but can't communicate with each other)? It
s
Added the step about the version in this file -
https://ignite.apache.org/latest
--
Denis
On Wed, Jul 18, 2018 at 9:10 AM Anton Vinogradov wrote:
> It looks like we have to update release page with steps forgotten on this
> iteration.
>
>
> ср, 18 июл. 2018 г. в 18:16, Andrey Gura :
>
>> Latest
Hi folks,
Artem's proposal might simplify and make our doc tickets tracking less
error-prone. The current approach implies that a contributor keeps in mind
what needs to go to the docs. If he/she has a good memory, a doc JIRA
counterpart will be created once the contribution is accepted. But the
p
Hi Dmitriy,
Yes, I would have this tool at hands soon as I check out Ignite repo and
start setting it up. However, instead of a new repo let's place it under
{ignite}/dev-tools folder. What do you think?
--
Denis
On Wed, Jul 18, 2018 at 4:37 AM Dmitry Pavlov wrote:
> Hi Igniters,
>
> There is
Hi Dmitriy,
The whole year has passed since this initiative launch, hell, the times
passes by :)
What would be the benefits of having the tool in the Apache repo? Does it
simplify the things for us.
--
Denis
On Wed, Jul 18, 2018 at 3:59 AM Dmitry Pavlov wrote:
> Hi Igniters,
>
> Almost 1 year
Joel Lang created IGNITE-9031:
-
Summary: SpringCacheManager throws AssertionError during Spring
initialization
Key: IGNITE-9031
URL: https://issues.apache.org/jira/browse/IGNITE-9031
Project: Ignite
GitHub user mulugetam opened a pull request:
https://github.com/apache/ignite/pull/4381
Adding experimental support for Intel Optane DC Persistent Memory
Ignite, when persistence mode is enabled, stores data and indexes on disk.
To minimize the latency of disks, several tuning optio
Hi Maxim,
Sure, thank you for this idea.
I've accumulated notification types and rules here:
https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again#MakeTeamcityGreenAgain-NotificationTypes
Sincerely,
Dmitriy Pavlov
ср, 18 июл. 2018 г. в 13:59, Maxim Muzafarov :
> Dmitry,
Peter Ivanov created IGNITE-9030:
Summary: Apache Ignite 2.7 Linux packages version update
Key: IGNITE-9030
URL: https://issues.apache.org/jira/browse/IGNITE-9030
Project: Ignite
Issue Type:
GitHub user x-kreator opened a pull request:
https://github.com/apache/ignite/pull/4380
Ignite 8719
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/x-kreator/ignite ignite-8719
Alternatively you can review and apply these change
It looks like we have to update release page with steps forgotten on this
iteration.
ср, 18 июл. 2018 г. в 18:16, Andrey Gura :
> Latest version is updated.
>
> Thanks!
> On Wed, Jul 18, 2018 at 4:50 PM Dmitriy Setrakyan
> wrote:
> >
> > Andrey Gura, can you please update it?
> >
> > D.
> >
> >
Dmitry,
The goal I had in mind by proposing that suggestion was to rectify the
fact that JIRA issues for documentation are created on an ad-hoc basis,
and often issues are created when the lack of documentation becomes an
issue for somebody. So we need to be more proactive.
I think manual tr
Latest version is updated.
Thanks!
On Wed, Jul 18, 2018 at 4:50 PM Dmitriy Setrakyan wrote:
>
> Andrey Gura, can you please update it?
>
> D.
>
> On Wed, Jul 18, 2018 at 6:34 AM, Dmitry Pavlov
> wrote:
>
> > Hi Ilya,
> >
> > Thank you for noticing this.
> >
> > We should somehow update https://i
The Apache Ignite Community is pleased to announce the release of
Apache Ignite 2.6.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 scale.
This release fi
Pavel, thakns for help. I've uploaded NuGet packages. Announce will be
sent shortly.
On Tue, Jul 17, 2018 at 9:59 PM Denis Magda wrote:
>
> Andrey G.,
>
> As a PMC member and release manager of 2.6, could you please help the folks
> to finish this step?
>
> --
> Denis
>
> On Tue, Jul 17, 2018 at 9
> It can seem not important, but saves a minute for everyone.
No, it actually does seem important when you think about it :) Thanks for the
suggestion.
Let me correct this then.
The issue is
IGNITE-6826: Change default DiscoverySpi ipFinder type for examples
https://issues.apache.org/jira/browse
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4379
GG-13998 IGNITE-5975 Fixed hang on concurrent node stop and continuous query
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ign
Hi Stanislav,
I wish this push will have effect.
Just two proposals that will help Igniters to easily jump into such emails:
1. Include ticket short description into subject, not only number.
2. Include link to JIRA issue into body so it could be easily clicked to
find out details.
It can seem no
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4280
---
Andrey Gura, can you please update it?
D.
On Wed, Jul 18, 2018 at 6:34 AM, Dmitry Pavlov
wrote:
> Hi Ilya,
>
> Thank you for noticing this.
>
> We should somehow update https://ignite.apache.org/latest data. I guess
> PMCs or site admin can do this update.
>
> Sincerely,
> Dmitriy Pavlov
>
> ср
Hi Ilya,
Thank you for noticing this.
We should somehow update https://ignite.apache.org/latest data. I guess
PMCs or site admin can do this update.
Sincerely,
Dmitriy Pavlov
ср, 18 июл. 2018 г. в 16:31, Ilya Kasnacheev :
> Hello!
>
> Since we have releases 2.6.0, can we perhaps prop up the no
Hi Igniters,
There is a small but annoying issue with examples using MulticastIpFinder by
default.
The JIRA is IGNITE-6826.
AntonK and DmitriiR have suggested PRs to fix this, but PavelT had some
concerns and the fix stuck as the result.
Pavel, could you please suggest necessary changes to th
Hello!
Since we have releases 2.6.0, can we perhaps prop up the node start
message, which is currently still:
[16:28:05] New version is available at ignite.apache.org: 2.4.0
Regards,
--
Ilya Kasnacheev
2018-07-17 21:59 GMT+03:00 Denis Magda :
> Andrey G.,
>
> As a PMC member and release mana
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4372
---
Hi Artem,
I sometimes receive feedback that Ignite docs has potential for
improvement, while I found our docs quite intuitive and simple to
understand. So if experienced tech writer will join community it could
benefit all of us, and users, of course. So you're very welcome to the
community!
Abou
Github user sk0x50 closed the pull request at:
https://github.com/apache/ignite/pull/4353
---
Github user sk0x50 closed the pull request at:
https://github.com/apache/ignite/pull/2692
---
Github user sk0x50 closed the pull request at:
https://github.com/apache/ignite/pull/3261
---
Github user sk0x50 closed the pull request at:
https://github.com/apache/ignite/pull/4163
---
Github user sk0x50 closed the pull request at:
https://github.com/apache/ignite/pull/2683
---
Github user sk0x50 closed the pull request at:
https://github.com/apache/ignite/pull/2490
---
Yes! Just deprecate getAll() and change default keepAll for scans to false.
--Yakov
2018-07-18 13:39 GMT+03:00 Alexey Goncharuk :
> Folks,
>
> There is no need to add getNext() method because the object we are
> discussing is already an iterator. Then, to summarize the solution, we are
> going t
Maxim, I checked and it seems that send retry count is used only in cache
IO manager and the usage is semantically very far from what I suggest.
Resend count limits the attempts count, while I meant successfull send but
possible problems on supplier side.
--Yakov
2018-07-17 19:01 GMT+03:00 Maxim
Hi Igniters,
Being a technical writer, I'm going to contribute to Ignite's
documentation, and I believe documentation is an important part of every
product, especially such a complex product as Apache Ignite.
I'd like to put forward a suggestion on how to increase our chances of
making Ignit
Hi Igniters,
There is one mode widely used tool in Apache Ignite, abbreviation plugin
for Intelli J Idea. This plugin is used by almost all experienced Ignite
contributors.
I would like to say thanks to all contributors which created this plugin:
vkazakov, sevdokimov, daradurvs, agoncharuk. And b
Hi Igniters,
Almost 1 year has passed since Make Teamcity Green Again was initially
proposed. During this process we managed to get almost successful Run Alls
in master, but currently regressions still occur. We all tried a lot of
things: careful examination of PR tests, continuous monitoring of m
Dmitry,
Got it. Thanks!
I've found brief MTCGABot description here [1].
Can we also add there this notification rules?
[1]
https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again#MakeTeamcityGreenAgain-MTCGABot
ср, 18 июл. 2018 г. в 12:52, Dmitry Pavlov :
> Hi Maxim,
>
> N
Folks,
There is no need to add getNext() method because the object we are
discussing is already an iterator. Then, to summarize the solution, we are
going to deprecate getAll() method and set keepAll flag to false for scan
query.
Agree?
пн, 16 июл. 2018 г. в 23:40, Dmitriy Setrakyan :
> On Mon,
Alexey Goncharuk created IGNITE-9029:
Summary: TcpDiscoverySpiMBeanTest flaky-fails in master
Key: IGNITE-9029
URL: https://issues.apache.org/jira/browse/IGNITE-9029
Project: Ignite
Issue
Hi Maxim,
Notification will be send for each sequential group of builds having
failures 3+ times in a row. Let's define 0 as success, 1 as failure.
So history 01110111 will generate two notifications. First
transition 0->1 can be bug introduced test failure. This bug can be fixed
with som
Ilya Borisov created IGNITE-9028:
Summary: Web console: update to Babel 7
Key: IGNITE-9028
URL: https://issues.apache.org/jira/browse/IGNITE-9028
Project: Ignite
Issue Type: Improvement
Dmitry,
Will this notification continously send on new failure fot particular
test-case if we already have JIRA ticket for investigation? Should we mute
this test on TC to stop notifications?
вт, 17 июл. 2018 г. в 22:30, Dmitry Pavlov :
> Odd flaky tests notifications were fixed.
>
> If test cha
GitHub user nizhikov opened a pull request:
https://github.com/apache/ignite/pull/4378
IGNITE-8915: NPE on local sql query for client node.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nizhikov/ignite IGNITE-8915
Alternativel
55 matches
Mail list logo
