Hi Roman,
thank you for stepping in and fixing tests.
The fix was merged into all branches.
Sincerely,
Dmitriy Pavlov
ср, 3 окт. 2018 г. в 22:30, Roman Kondakov :
> Dmitriy, Vladimir,
>
> We added an extra memory region for TxLog and this change wasn't
> reflected in .Net tests.
&
Hi Nikolay, Igniters,
I've added the link to notes, and (as follow up related to the blockers/
non-blockers discussion) added several attributes of blockers. Please
review if you have a minute.
Sincerely,
Dmitriy Pavlov
вт, 2 окт. 2018 г. в 14:49, Nikolay Izhikov :
> Dmitriy, thank you.
&g
Bots from dev list), please start a separate
discussion. As part of this discussion, I would like we come to an
agreement about the creation of the list and forwarding TC Bot review
comments there.
ср, 3 окт. 2018 г. в 18:42, Dmitriy Pavlov :
> Yes, by Igniters, who will subscribe to it us
...@apache.org (GitBox, TC Bot
repository).
g...@git.apache.org (GitHub), so regular PRs to Ignite will be forwarded as
is.
ср, 3 окт. 2018 г. в 18:36, Petr Ivanov :
> Will that list be read at all?
>
>
>
> > On 3 Oct 2018, at 17:24, Dmitriy Pavlov wrote:
> >
> > Hi Ignit
need your help to fix these test.
Assert fails 3 instead of 4 in test validation, could you please step in
and help with fixing this?
Sincerely,
Dmitriy Pavlov
сб, 29 сент. 2018 г. в 12:29, Dmitriy Pavlov :
> Vladimir, I agree more with Andrey's fix in the parity test, because it
> di
Hi Alexey,
Could you please assist with fixing test?
Sincerely,
Dmitriy Pavlov
сб, 29 сент. 2018 г. в 12:23, Dmitriy Pavlov :
> Folks,
>
> both tests are failed in ignite-2.7 IgniteStandByClusterTest.testSimple
> <https://ci.ignite.apache.org/project.html?projectId=Ign
separate list for these
notifications may be a solution.
Sincerely,
Dmitriy Pavlov
fixes instead.
Nikolay,
we've passed only scope freeze, but not code freeze. I've mentioned we
should discuss ticket including in our process, and features are
prohibited, but please note it is a draft for now.
Sincerely,
Dmitriy Pavlov
ср, 3 окт. 2018 г. в 13:38, Nikolay Izhikov :
> He
Denis, Alexey,
thank you for work you do to make Ignite more recognizable.
Don't forget to encourage contributors to come not only to ML but to core
and to other modules as well :)
Sincerely,
Dmitriy Pavlov
ср, 3 окт. 2018 г. в 6:29, Denis Magda :
> Alexey,
>
> Thanks for spreading
the bugs
were introduced. I feel a number of bugs reported recently are all
connected to WalManager, and these bugs may come from just a couple of
fixes. PDS tests were quite stable last time, so I think it is possible to
find out why WAL crashes and hangs.
Sincerely,
Dmitriy Pavlov
ср, 3 окт
and revert these commit(s) from 2.7 and research
these failures in master (with no rush).
Sincerely,
Dmitriy Pavlov
вт, 2 окт. 2018 г. в 23:54, Vladimir Ozerov :
> Andrey, Anton,
>
> How do you conclude that these tickets are blockers? What is the impact to
> users and in what circums
compile and run well.
I've updated checklist, thank you for pointing to this.
So I suggest keeping existing naming of TcpDiscoveryElbIpFinder as it is
part of API.
Sincerely,
Dmitriy Pavlov
вт, 2 окт. 2018 г. в 21:04, uday kale :
> Thanks for the review Stan.
> I renamed the existing
it
easy to understand what method creates.
Sincerely,
Dmitriy Pavlov
ср, 12 сент. 2018 г. в 20:34, Denis Magda :
> Hello Nikolay,
>
> Excellent progress, look forward to seeing the TDE released in 2.7!
>
> --
> Denis
>
> On Wed, Sep 12, 2018 at 2:47 AM Nikolay Izhikov
>
/Release+Process
Please find a minute and take a look. Feedback, as always, is more than
welcome.
Sincerely,
Dmitriy Pavlov
Hi Anton,
I definitely agree it is a blocker.
Sincerely,
Dmitriy Pavlov
вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov :
> Hi Igniters.
>
> I have one more possible blockers - deadlock in archiver -
> https://issues.apache.org/jira/browse/IGNITE-9761. I almost fixed it.
> It
gt; > >
> > > > В Пн, 01/10/2018 в 16:13 +0300, Andrey Gura пишет:
> > > > > Agree with Andrey.
> > > > >
> > > > > IGNITE-9723 will be merged to ignite-2.7 branch soon.
> > > > > On Mon, Oct 1, 2018 at 3:56 PM Andrey Kuznetso
I agree, which why I initially asked about code freeze (actually it was
scope freeze, I apologize).
So I prefer to create a new suite and give us some time to run these new
tests in master.
пн, 1 окт. 2018 г. в 19:34, Nikolay Izhikov :
> Alex, Saikat.
>
> As I can see there is work to be done
, after the freeze, only bug/test fixes can
be merged to release branch.
Hi Nikolay,
could you please announce that code freeze happened?
Sincerely,
Dmitriy Pavlov
пн, 1 окт. 2018 г. в 3:58, Saikat Maitra :
> Hi Alex, Nicolay
>
> As discussed with Andrew the changes looks good. Would
list is not a log of community actions; it is the principal place where
discussion runs. I sincerely hope all similar decisions will be building on
the dev list.
Sincerely,
Dmitriy Pavlov
вс, 30 сент. 2018 г. в 10:49, Nikolay Izhikov :
> Hello, guys.
>
> I moved SG tasks to 2.8.
>
&
will also be fixed before 2.7
Sincerely,
Dmitriy Pavlov
пт, 28 сент. 2018 г. в 14:43, Павлухин Иван :
> Hi guys!
>
> By the way, is it practically feasible to revert a single commit without
> making harm? If I am getting it right in current case reverting commit will
> lead to com
()` remembers deactivated state and doesn't
> check current state.
>
> 2018-09-20 18:41 GMT+03:00 Dmitriy Pavlov :
>
> > Hi,
> >
> > IgniteStandByClusterTest seems to fail, Dmitriy G., Ivan, would it be
> > reasonable to revert commit?
> >
> &
vote goes to option *a*.
> > I think we should release 2.7 with the bunch of new cool features.
> > *AND* we should plan 2.8 release at the end of the year with SG redesign
> > and MVCC stabilization tasks.
> >
> > Anyway, while we preparing release a lot of things can happen.
&
I've checked run.
There are no suspicious test failures here, all failures are more or less
the same with the master.
пт, 28 сент. 2018 г. в 20:03, Dmitriy Pavlov :
> Hi David,
>
> Snapshot Dependency Error is TeamCity term means some from dependent
> builds failed.
>
> Be
Hi David,
Snapshot Dependency Error is TeamCity term means some from dependent builds
failed.
Because some percent of tests have constant floating failures, almost all
runs will get this error.
I will do some tests validation shortly.
Sincerely,
Dmitriy Pavlov
пт, 28 сент. 2018 г. в 15:17
disagree. There are no leaders in open source, just
do'ers.
By do'ers here I mean Nikolay and Vyacheslav. For me, their conclusion has
more weight here. If Vladimir is ready to lead an additional release for SG
and SG developers agree, it works for me.
Sincerely,
Dmitriy Pavlov
пт, 28 сент. 2018 г
Hi,
These tests were recently unmuted, but not contributed. I would appreciate
if someone can provide more info why these tests were unmuted.
Sincerely,
Dmitriy Pavlov
пт, 28 сент. 2018 г. в 17:47, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled. You are
Hi, this failure does not seem to be a new failure.
This test was recently unmuted, and the Bot considers it as new.
Sincerely,
Dmitriy Pavlov
пт, 28 сент. 2018 г. в 17:17, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled. You are more than
> welc
of the review, I see
no reasons to reject their contribution, even if we need to revisit our
agreements and wait for a couple of days more.
Am I missing some reason why dates are so fundamentally important to you?
Sincerely,
Dmitriy Pavlov
пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan :
> If servi
ors to fix missed
test failures and they managed to do it in 1-2 days, I'm waiting these test
to be fixed by Ignite veteran(s) for 11 days.
Sincerely,
Dmitriy Pavlov
пт, 28 сент. 2018 г. в 13:16, Vladimir Ozerov :
> Andrey,
>
> This is not a fix, but a hack, which covers real state of
ecide whether
> something goes to 2.7”.
>
> пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov :
>
> > No, it is up to the community to discuss after their review results.
> >
> > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov :
> >
> > > Dmitriy,
> > >
Hi Maxim,
Once 1) you are sure that commit is related to the failure, and 2) in case
contributors are not responding,
please let me know, probably we need to open one more separate topic about
revert.
Sincerely,
Dmitriy Pavlov
пт, 28 сент. 2018 г. в 11:15, Maxim Muzafarov :
> Andrey, Dmi
delayed?
>
> пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov :
>
> > My point we can wait a bit for services because
> > 1 we are open-minded and we don't have outside pressure to do release in
> > October
> > 2 and services it is not some new feature, which sud
ready, it should be
> moved to future release, instead of shifting release. The sole reason to
> have strict dates when decisions are made is to let release happen.
>
>
>
> On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov
> wrote:
>
> > Vladimir, I'm not searching
gt; think about the impact and project priorities first, instead of trying to
> apply the some sort rules blindly. We are not robots.
>
> On Fri, Sep 28, 2018 at 10:19 AM Dmitriy Pavlov
> wrote:
>
> > Hi Vladimir,
> >
> > https://issues.apache.org/jira/browse/IGN
you suggest instead?
Sincerely,
Dmitriy Pavlov
пт, 28 сент. 2018 г. в 2:40, Dmitriy Setrakyan :
> Let's not revert any commits yet. Can we find out who did the commit and
> why he/she is not fixing the test?
>
> D.
>
> On Thu, Sep 27, 2018 at 4:21 PM Vyacheslav Daradur
Hi Vladimir,
https://issues.apache.org/jira/browse/IGNITE-9320 is named configuration
finalization.
Why finalization was considered as done without tests passing?
Why can't ve revert finalization change, re-do finalization with passing
tests and merge changes?
Sincerely,
Dmitriy Pavlov
пт, 28
who privately discuss
something.
Sincerely
Dmitriy Pavlov
чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur :
> Hi Igniters!
>
> As I have written about Service Grid before [1] I'm finalizing the
> solution to be sure that implementation is reliable.
>
> About including it in 2.7, if
Hi,
I'm grateful for contributions made in that area, but it seems folks don't
have time to fix the test.
Tomorrow I'm going to revert commit.
It seems it is the only way we can keep master more or less green.
ugh, and can be a good candidate for fixing before 2.7 release.
>
> Do you agree?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-9731
>
> чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov :
>
> > I need Vhyacheslav's opinion to be absolutely sure what status is now.
> &g
Hi Alexander,
I've added you to the list of contributors. Now you can assign an issue to
yourself.
Should you have any question, please do not hesitate to ask.
Welcome to the Apache Ignite Community!
Sincerely,
Dmitriy Pavlov
Couple links that can help you to onboard.
https://cwiki.apache.org
gt;> was
>> questionable whether it gets added to the release or not.
>>
>> *Vladislav*, could you please shed some light on the current status of the
>> service grid?
>>
>> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov
>> wrote:
>>
>>
mir Ozerov :
> Dmitriy,
>
> This is an outcome of current state of Service Grid - it is not ready. We
> never committed to have it to 2.7. Our goal was to try to include it into
> 2.7.
>
> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov
> wrote:
>
> > Could you please pro
/fix/test it properly.
>
> On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov
> wrote:
>
> > I agree, and I prefer four weeks for stabilization* (1 Oct - 29 Oct)
> >
> > Do I understand it correctly: Service Grid is still in scope, isn't it? I
> > find it very im
to the
reviewer field.
So reviewer is someone, who is ready and going to do the review. Unless we
not sure who will do a review, mention process continues to work.
Sincerely,
Dmitriy Pavlov
https://lists.apache.org/thread.html/c6013b99940de32aae831a0b76e8fd53febe5040e9e0d67abb4f62a5
I agree, and I prefer four weeks for stabilization* (1 Oct - 29 Oct)
Do I understand it correctly: Service Grid is still in scope, isn't it? I
find it very important.
чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov :
> Hello, Vova.
>
> Thank you for clear release status.
> I'm +1 for your
Hi Nikolai,
sure, you are more than welcome to update AI wiki, not only about TC bot
but about all you need to understand during contributing to Ignite.
I've set needed permissions, please check.
Sincerely,
Dmitriy Pavlov
чт, 27 сент. 2018 г. в 15:44, Nikolai Kulagin :
> Hi, Dmitrii
&g
Fixed, now the fix is in the ignite-2.7 branch.
ср, 26 сент. 2018 г. в 23:18, Dmitriy Pavlov :
> Oops, my fault. It seems I forgot to cherry-pick to 2.7, but I resolved
> ticket with 2.7 assigned.
>
> I will fix it tomorrow.
>
> ср, 26 сент. 2018 г. в 21:52, Denis Magda :
Hi,
I think we can ignore the failure. This test is reported as a failure
because of strange notification of init method as a standalone test.
Actually, initialization is failed as flaky.
Sincerely,
Dmitriy Pavlov
чт, 27 сент. 2018 г. в 8:31, :
> Hi Igniters,
>
> I've detected some
>
> Please try to reach out to gene...@incubator.apache.org
>
> --
> Denis
>
> On Wed, Sep 26, 2018 at 9:04 AM Dmitriy Pavlov
> wrote:
>
> > Hi Igniters,
> >
> > It seems to me, that the project description at
> > http://people.apache.org/phonebook.html is a
e who use Ignite in
> production.
>
> Are we getting it in 2.7?
>
> --
> Denis
>
> On Wed, Sep 26, 2018 at 10:11 AM Dmitriy Pavlov
> wrote:
>
> > Hi Igniters,
> >
> > Thanks to everyone, who has participated in this discussion and shared
> > t
questions.
Sincerely,
Dmitriy Pavlov
пн, 24 сент. 2018 г. в 18:52, Pavel Pereslegin :
> Andrei,
> I totally agree with you and I think that "ClusterMetrics" should also
> be fixed, I'm just not sure that we should include this change in the
> same ticket.
> пн, 24 сент. 2018
to update product description at the Apache site. Is
it easy to do?
The same issue is related to https://projects.apache.org/project.html?ignite
but here I can ask at the ComDev list to update.
Sincerely,
Dmitriy Pavlov
in the review process
are strongly appreciated.
Sincerely,
Dmitriy Pavlov
ср, 15 авг. 2018 г. в 19:38, Dmitriy Pavlov :
> Hi Igniters,
>
> I took a look at the proposed contribution
> https://issues.apache.org/jira/browse/IGNITE-8617 and PR
> https://github.com/apache/ignite/pull/40
Dmitriy, thank you for your efforts and for creating this page. A lot of
Igniters were asking about it.
ср, 26 сент. 2018 г. в 14:46, Dmitrii Ryabov :
> Hello, Igniters!
>
> You've all seen the messages with new failures from MTCGA.Bot.
>
> But the bot can also be used to analyze TeamCity runs
contribution
to pick up into a review.
Please share your vision about the idea of adding a reviewer field (type:
user) in addition to the assignee field.
If we agree I will try to ask the Infra team on Friday 28.09.
Sincerely,
Dmitriy Pavlov
1000 PR doesn't sound like big issue for me.
>
> My vote goes strong to GiHub user interface.
> I think we should have closer integration with GitHub, not Jira.
>
> Jira is about tickets and project management.
> GitHub is about code, commits and patches.
> We test patch, not ti
is not a valid situation in the majority of cases and How To
Contribute asks to avoid it. The bot can ignore closed PRs and the bot can
expect there is only one open PR per ticket.
Sincerely,
Dmitriy Pavlov
пн, 24 сент. 2018 г. в 23:41, Nikolay Izhikov :
> Hello, Dmitriy.
>
> > But it could be a
bot early (probably author added some fixes)
but still in PA state, the bot will check comments list and find possible
new mentions (made after the previous build complete date). If it finds
such comments it goes to step 1 (trying to find only new builds available).
What do you think?
Sincerely,
Dmit
Thank you, Petr!
Done with the Bot. I will not enable notifications to dev. list.
A user can come to its own preferences page and enable "Notify on all
failures in ignite-2.7"
пн, 24 сент. 2018 г. в 19:18, Petr Ivanov :
> Done with trigger.
>
>
>
> > On 24 Sep 20
Hi Nikolay, Petr
could you please create triggers for nightly builds?
I will also add the branch to be tracked to TC Bot.
Sincerely,
Dmitriy Pavlov
пн, 24 сент. 2018 г. в 18:24, Nikolay Izhikov :
> Hello, Igniters.
>
> I've created branch for an Apache Ignite 2.7 release [1]
> Pl
Hi Igniters, I've found Parity check test was muted.
The test itself contains the possibility to exclude property. No reason to
mute this test.
Could you please ignore property in code?
Sincerely,
Dmitriy Pavlov
пн, 17 сент. 2018 г. в 17:25, :
> Hi Ignite Developer,
>
> I am
Hi Val, many thanks for the review.
ср, 12 сент. 2018 г. в 20:35, Valentin Kulichenko <
valentin.kuliche...@gmail.com>:
> Yes, will try to review this week.
>
> -Val
>
> On Wed, Sep 12, 2018 at 10:24 AM Dmitriy Pavlov
> wrote:
>
> > Hi Val,
> >
> >
Awesome, thanks! Added you to list of contributors.
Feel free to create a new page under
https://cwiki.apache.org/confluence/display/IGNITE/Testing+and+benchmarking
Sincerely,
Dmitriy Pavlov
пн, 24 сент. 2018 г. в 15:39, Dmitrii Ryabov :
> I signed up. My username - somefire.
>
> 2018
++1 Only one concern - the domain name is now GridGain. I will ask infra
about Apache domain, but it will require some time to be done.
пн, 24 сент. 2018 г. в 15:07, Dmitrii Ryabov :
> Hello, Igniters!
>
> I propose to update the "How to Contribute" page to include TeamCity
> Helper's JIRA
Dmitrii,
could you please sign up to the wiki and share your ID. I will set
necessary permissions.
Sincerely,
Dmitriy Pavlov
пн, 24 сент. 2018 г. в 14:57, Dmitrii Ryabov :
> Hello, Igniters!
>
> I propose to create page about TeamCity Helper on the wiki and move here
> information
Hi Igniters,
It seems it is duplicate. But anyway Hadoop needs to be fixed.
Sincerely,
Dmitriy Pavlov
пн, 24 сент. 2018 г. в 0:14, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
> If your changes can lead
from all community and grant
agreement signing.
So I suggest creating PR.
Sincerely,
Dmitriy Pavlov
пн, 24 сент. 2018 г. в 13:03, akurbanov :
> Hello Igniters,
>
> I have implemented small community extension to use Apache Ignite as
> backing
> repository for session clustering with
background tasks within bot
(time, result or exception).
- Async start and activation of Ignite, - service is up and running
immediately after web server start, but data from Ignite not returned (HTTP
code 418 is returned in this case).
Sincerely,
Dmitriy Pavlov
Got it, thanks! I'll watch this ticket too.
пт, 21 сент. 2018 г. в 20:16, Dmitrii Ryabov :
> Hi, Dmitiy,
>
> I created ticket [1] 3 days ago.
>
> [1] https://issues.apache.org/jira/browse/INFRA-17032
>
> 2018-09-19 20:51 GMT+03:00 Dmitriy Pavlov :
>
>> Hi Dmitriy
Hi Anton, Petr,
I confirm that TC Bot writes a lot of stuff, so it may create problems for
Cassandra storage.
The latest version of Bot has optimization of data saving, and its reduces
amount of data to be saved to disk. But still, disc separation is a better
solution.
Sincerely,
Dmitriy Pavlov
.
I've done some re-loading of builds from TC, so more or less master
statistic is updated.
In the background, I will try to restore some data, and hopefully,
Apache Ignite DB reading utility (discussed by Alex G and Dmitriy G) will
be available soon.
Sincerely,
Dmitriy Pavlov
.
Sincerely,
Dmitriy Pavlov
пт, 21 сент. 2018 г. в 12:28, Maxim Muzafarov :
> Dmitry, Dmitry
>
> I've run MTCGA.Bot with additional commenting to JIRA [1] and bot have
> shown the report [2] of TC Run all without mentioning
> `IgniteOptimizationDateFuncSpec` test failure.
>
> Any
gent. And the only migration option would be Java 11, as neither Java 9,
> not Java 10 will be supported since the next week.
>
> On Thu, Sep 20, 2018 at 11:23 PM Dmitriy Pavlov
> wrote:
>
> > Hi Vladimir,
> >
> > Do you know if update notifier can get and record java ver
amount of time to migrate.
Sincerely,
Dmitriy Pavlov
чт, 20 сент. 2018 г. в 23:00, Vladimir Ozerov :
> Igniters, we have a problem.
>
> *TL;DR;*
> Ignite may be seriously broken in Java 11. This affects ignite.sh,
> Hibernate integration, JTA integration. And we cannot test it before co
Hi Anton, do you know someone else is facing with this issue?
Could it be a local problem?
чт, 20 сент. 2018 г. в 22:18, Anton Vinogradov :
> Still, see the same issues.
>
> Denis,
>
> Could you please prioritize the fix?
>
> вт, 18 сент. 2018 г. в 14:01, Anton Vinogradov :
>
> > Also, I see
г. в 21:15, Dmitriy Pavlov :
> Why do you think there is no consensus?
>
> I have no clue that by default failure handler should fail all test.
>
> чт, 20 сент. 2018 г. в 21:10, Andrey Kuznetsov :
>
>> I've created [1] to address this.
>>
>> Dmitriy, I like your
; > TcpDiscoverySpi#simulateNodeFailure
> >
> > BTW, I would like to remove this method at all from production code.
> >
> > On Thu, 20 Sep 2018 at 19:43 Dmitriy Pavlov
> wrote:
> >
> > > But the totally ideal situation would be finding a way to fail the tes
But the totally ideal situation would be finding a way to fail the test by
default, not only stopping a node.
Some time ago I've created https://issues.apache.org/jira/browse/IGNITE-8227 to
find out a way to do so.
чт, 20 сент. 2018 г. в 19:40, Dmitriy Pavlov :
> ++1
>
> чт, 20 сент.
++1
чт, 20 сент. 2018 г. в 19:39, Andrey Kuznetsov :
> Igniters,
>
> While running tests I see a lot of ignored critical failures caused by
> {{NoOpFailureHandler}} that we use by default. In some tests, of cource,
> critical failures are the part of normal workflow, but in the majority of
>
Hi,
IgniteStandByClusterTest seems to fail, Dmitriy G., Ivan, would it be
reasonable to revert commit?
Dmitriy Ryabov, is it related to recent fix or is it a standalone problem?
Sincerely,
Dmitriy Pavlov
пн, 17 сент. 2018 г. в 18:45, Dmitrii Ryabov :
> Looks like problem I had descri
Hi Roman, Vladimir,
Is there any news about this failure? IgniteConfigurationParityTest seems
to fail.
Can we revert initial commit and re-merge with tests fixes?
Sincerely,
Dmitriy Pavlov
вт, 18 сент. 2018 г. в 12:22, Roman Kondakov :
> Hi, Dmitriy!
>
> Vladimir assured me in
can't enforce someone
to do something faster or in more right manner. Why don't suggest help
instead?
Sincerely,
Dmitriy Pavlov
чт, 20 сент. 2018 г. в 12:29, Paul Anderson :
> Dimitiry, Re: IGNITE-9298 ... this is my first contribution, don't know who
> is reviewing the code, I d
it
to the next version instead of the nearest one.
Sincerely,
Dmitriy Pavlov
чт, 20 сент. 2018 г. в 3:54, Ray :
> Hello, Igniters.
>
> Is there any specific reason why this ticket is removed from 2.7 scope?
> I think this ticket is important for both usability and performance.
> With
Hi Dmitriy Ryabov,
could you please create and share INFRA ticket to disable comment
forwarding to the dev list?
Sincerely,
Dmitriy Pavlov
ср, 19 сент. 2018 г. в 19:02, GitBox :
> SomeFire commented on a change in pull request #14: Performance
> URL:
> https://github.com/apache/ignite
Dmitriy Ryabov,
Thank you for your comments to PR14. Merged. Could you please take a look
at the proposed changes?
Idea is that for hot method getBuildHistory we can limit the number of
builds to be loaded from TC REST.
Sincerely,
Dmitriy Pavlov
ср, 19 сент. 2018 г. в 20:43, GitBox
Dmitriy Pavlov created IGNITE-9648:
--
Summary: Improve doc and javadoc for Ignite distrubuted lock
Key: IGNITE-9648
URL: https://issues.apache.org/jira/browse/IGNITE-9648
Project: Ignite
Hi Dmitrii,
thank you for making an additional announce.
And I appreciate your efforts to make this contribution happen.
During Bot existence it was always developed based on Igniters feedback,
so, as always, your feedback is very welcome.
Sincerely,
Dmitriy Pavlov
ср, 19 сент. 2018 г. в
Hi Igniters,
Who could advise about possible reasons? Spring data version was updated
recently, but examples tests seem to be passing.
If it is not a local problem then I consider this ticket is a blocker of
2.7.
Sincerely,
Dmitriy Pavlov
ср, 19 сент. 2018 г. в 11:44, Stepan Pilschikov (JIRA
Hi Dmitriy,
Probably we can standalone page for the Bot description because the Bot
became standalone module not too much related to MTCGA.
If you would like to contribute some description please share your wiki
username, I will grant necessary permission.
Sincerely,
Dmitriy Pavlov
ср, 19 сент
gt; knows everything will fit there. If during the preloading we detect that
> the RAM is exhausted we can halt it and print out a warning.
>
> --
> Denis
>
> On Tue, Sep 18, 2018 at 2:10 PM Dmitriy Pavlov
> wrote:
>
> > Hi,
> >
> > I totally support the idea o
).
Sincerely,
Dmitriy Pavlov
вт, 18 сент. 2018 г. в 21:36, Denis Magda :
> Folks,
>
> Since we're adding a method that would preload a certain partition, can we
> add the one which will preload the whole cache? Ignite persistence users
> I've been working with look puzzled on
Hi Paul.
There are 2 PRs linked to that ticket. Who is reviewing your changes?
Branch for 2.7 is still master, so if your changes are reviewed and
accepted soon it will be in 2.7.
Sincerely,
Dmitriy Pavlov
вт, 18 сент. 2018 г. в 16:22, Paul Anderson :
> Hi, may I ask for IGNITE-9
> On 18 Sep 2018, 16:55, at 16:55, Dmitriy Pavlov
> wrote:
> >Hi, is it related to some contribution? If not, I propose
> >u...@ignite.apache.org as a better place to ask.
> >
> >вт, 18 сент. 2018 г. в 18:43, wt :
> >
> >> i have the following cl
Hi, is it related to some contribution? If not, I propose
u...@ignite.apache.org as a better place to ask.
вт, 18 сент. 2018 г. в 18:43, wt :
> i have the following class
>
> [QuerySqlField]
> public int vd { get; set; }
> [QuerySqlField]
> public long
to remind about tickets in dev list if there is no feedback from
Igniters.
Sincerely,
Dmitriy Pavlov
пн, 17 сент. 2018 г. в 21:17, David Harvey :
> I'm new to this process, and I've created three pull requests, and I'm
> trying to figure out how I can get some eyes to look at them.
>
>
he data usage`
> > > to choose the best technique in each case.
> > >
> > > For instance, it's not obvious what would take longer: multi-block
> reads
> > or
> > > 50 single-block reads issues
> > > sequentially. It strongly depends on used hardware under the ho
-Testof.NETAPIparitywithJavaAPI
recommendations?
Sincerely,
Dmitriy Pavlov
пн, 17 сент. 2018 г. в 17:25, :
> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
> *New test
Hi Igniters,
Roma Kondakov in private talk confirmed that test is failed because of
recent changes.
To be fixed under ticket: https://issues.apache.org/jira/browse/IGNITE-9390
Sincerely,
Dmitriy Pavlov
пн, 17 сент. 2018 г. в 16:42, :
> Hi Ignite Developer,
>
> I am MTCGA.Bot,
Hi, Actually there is no such plan for 2.7. In 2.7 we will probably switch
to 1.1.1.
Sincerely,
Dmitriy Pavlov
пн, 17 сент. 2018 г. в 5:22, kcheng.mvp :
> Is there any plan to migrate kafka 2.0 in ignite-kafka?
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
.
And one more concern from me is about selecting a right place in the system
to do such prefetch.
Sincerely,
Dmitriy Pavlov
вс, 16 сент. 2018 г. в 19:54, Vladimir Ozerov :
> HI Alex,
>
> This is good that you observed speedup. But I do not think this solution
> works for the product in
701 - 800 of 1052 matches
Mail list logo
