GitHub user antonovsergey93 opened a pull request:
https://github.com/apache/ignite/pull/5327
IGNITE-10085 Compressed files were made more user friendly.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Stanislav Lukyanov created IGNITE-10152:
---
Summary: Allow warming up data region before a node has joined
Key: IGNITE-10152
URL: https://issues.apache.org/jira/browse/IGNITE-10152
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5081
---
GitHub user pavlukhin opened a pull request:
https://github.com/apache/ignite/pull/5326
Test drive Junit4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite junit4
Alternatively you can review and apply
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5230
---
GitHub user dgovorukhin opened a pull request:
https://github.com/apache/ignite/pull/5328
Remove direct threadID call
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dgovorukhin/ignite master-remove-threadId
Alternatively you
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5235
---
zzzadruga opened a new pull request #59: IGNITE-10137 Add button 'Expand all'
on 'PR failures' page
URL: https://github.com/apache/ignite-teamcity-bot/pull/59
Add button 'Expand all' on 'PR failures' page. The button should show
additional information for all available lines.
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/5252
IGNITE-10106: Cache 5 test suite optimization
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10106
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5234
---
Ivan Bessonov created IGNITE-10142:
--
Summary: Cache 8 tests optimization
Key: IGNITE-10142
URL: https://issues.apache.org/jira/browse/IGNITE-10142
Project: Ignite
Issue Type: Improvement
Alexey Platonov created IGNITE-10141:
Summary: Cache 3 tests optimization
Key: IGNITE-10141
URL: https://issues.apache.org/jira/browse/IGNITE-10141
Project: Ignite
Issue Type:
Wayne, can you please share a reproducer for this problem that can be
launched from IDE?
--Yakov
Wayne, can you please share a reproducer for this problem that can be
launched from IDE?
--Yakov
GitHub user ibessonov opened a pull request:
https://github.com/apache/ignite/pull/5253
IGNITE-10142 Cache 8 tests optimization
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10142
Alternatively
Artem Malykh created IGNITE-10144:
-
Summary: Optimize bagging upstream transformer
Key: IGNITE-10144
URL: https://issues.apache.org/jira/browse/IGNITE-10144
Project: Ignite
Issue Type:
GitHub user aealeksandrov opened a pull request:
https://github.com/apache/ignite/pull/5255
Ignite 2.4.13
Created for team city run. Should not be merged.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Hi all,
I'm reviving this thread because it seems to me that it might be better to
go back to the combined in-memory and PDS suites now.
As usual, it is a long one, so feel free to skip to the TLDR.
The decision for the split was mostly driven by the desire to have shorter
time of suite runs.
It
Alexander created IGNITE-10143:
--
Summary: Cache operations hang after the cluster becomes disabled
Key: IGNITE-10143
URL: https://issues.apache.org/jira/browse/IGNITE-10143
Project: Ignite
Yury Babak created IGNITE-10145:
---
Summary: [ML] ROC AUC score
Key: IGNITE-10145
URL: https://issues.apache.org/jira/browse/IGNITE-10145
Project: Ignite
Issue Type: New Feature
PetrovMikhail created IGNITE-10146:
--
Summary: [TC Bot] Refresh missing prs while full reindex
Key: IGNITE-10146
URL: https://issues.apache.org/jira/browse/IGNITE-10146
Project: Ignite
Issue
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/5254
IGNITE-10141: Cache 3 tests optimization
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10141
Alternatively
SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add
visas caсhing and monitoring
URL: https://github.com/apache/ignite-teamcity-bot/pull/40#discussion_r231087806
##
File path:
SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add
visas caсhing and monitoring
URL: https://github.com/apache/ignite-teamcity-bot/pull/40#discussion_r231112646
##
File path:
SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add
visas caсhing and monitoring
URL: https://github.com/apache/ignite-teamcity-bot/pull/40#discussion_r231112615
##
File path:
SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add
visas caсhing and monitoring
URL: https://github.com/apache/ignite-teamcity-bot/pull/40#discussion_r231087525
##
File path:
SomeFire commented on a change in pull request #40: IGNITE-9939 [Tc Bot] Add
visas caсhing and monitoring
URL: https://github.com/apache/ignite-teamcity-bot/pull/40#discussion_r231103961
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/Visa.java
Github user SpiderRus closed the pull request at:
https://github.com/apache/ignite/pull/5213
---
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/5268
IGNITE-9840
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9840
Alternatively you can review and apply these
Igniters,
Any more comments on release notes?
On Tue, Nov 6, 2018 at 9:01 AM Nikolay Izhikov wrote:
> Vladimir, Thank you so much for this list!
>
> пн, 5 нояб. 2018 г., 23:25 Vladimir Ozerov voze...@gridgain.com:
>
> > Igniters,
> >
> > I assembled information about new features I am aware
Igniters,
I noted that the most common action I do on the devlist is clicking "Mark
As Read". All I see is JIRA and GitHub notifications. I simply counted last
100 threads and found that 89 of them are automated messages, 2 are MTCGA
bot messages, and 9 are real human-created threads.
Looks like
GitHub user pavlukhin opened a pull request:
https://github.com/apache/ignite/pull/5284
IGNITE-7955: MVCC TX: cache peek for key-value API
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7955
GitHub user Max-Pudov opened a pull request:
https://github.com/apache/ignite/pull/5286
Ignite 1.7.22
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.7.22
Alternatively you can review and apply
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4770
---
Vova, I've also started such topic about GitBox messages (
https://lists.apache.org/thread.html/1870ba56e0eb9e184d055ef2c84114ea43219d7c845036566f68e880@%3Cdev.ignite.apache.org%3E
).
But it seems no one reacted.
I agree to move out GitHub PR notifications + GitBox messages (see a
solution in the
Igor Sapego created IGNITE-10147:
Summary: CPP thin: Headers are not installed on make install
Key: IGNITE-10147
URL: https://issues.apache.org/jira/browse/IGNITE-10147
Project: Ignite
Issue
I just have a filter for Jira emails and automatically go into a different
folder for me.
On Tue, Nov 6, 2018 at 6:40 AM Dmitriy Pavlov wrote:
> Vova, I've also started such topic about GitBox messages (
>
>
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/5308
IGNITE-9989: Fixed jdbc v2 PK metadata
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9989
Stanislav Lukyanov created IGNITE-10150:
---
Summary: DisappearedCacheWasNotFoundMessageSelfTest fails with NPE
Key: IGNITE-10150
URL: https://issues.apache.org/jira/browse/IGNITE-10150
Project:
Guys,
I've found the following issue: [1]. It is quite local (only affects
Ignite C++ Linux build system) but quite critical too. I think it
should be included in 2.7.
What do you think?
[1] - https://issues.apache.org/jira/browse/IGNITE-10147
Best Regards,
Igor
On Tue, Oct 30, 2018 at 4:35
Hi!
I have filter for e-mail from JIRA (very useful, I can quick search issue
there without visiting JIRA).
And I'm just deleting tons of e-mails from GitBox & about PRs.
I don't know what for we need them?
May by we try to move GitBox & PRs-related mails first and see how it goes?
--
Alexey
Ilya Suntsov created IGNITE-10148:
-
Summary: Add aws s3 and elb configs to benchmarks/config
Key: IGNITE-10148
URL: https://issues.apache.org/jira/browse/IGNITE-10148
Project: Ignite
Issue
Anton Dmitriev created IGNITE-10149:
---
Summary: ML: Make ignite-tf.sh utility executable by default
Key: IGNITE-10149
URL: https://issues.apache.org/jira/browse/IGNITE-10149
Project: Ignite
GitHub user dmitrievanthony opened a pull request:
https://github.com/apache/ignite/pull/5313
IGNITE-10149: Make ignite-tf.sh executable by default.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
I should mention I disagree to remove JIRA issues as the first step. It
helps everyone to understand what other people are going to do in the
project. You always can comment if it is not the best approach, find a
duplicate issue, and you may suggest help.
PR notification is more or less
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/5315
IGNITE-10147: CPP Thin headers now installed on make install
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Can be Jira notifications united in some kind of daily digest?
Maybe we can add special filter (new tasks / updates during last 24 hours) with
notification scheme?
> On 6 Nov 2018, at 18:15, Dmitriy Pavlov wrote:
>
> I should mention I disagree to remove JIRA issues as the first step. It
>
Ivan Bessonov created IGNITE-10151:
--
Summary: Fix BinaryMarshallerSelfTest#testDefaultMapping test
Key: IGNITE-10151
URL: https://issues.apache.org/jira/browse/IGNITE-10151
Project: Ignite
ololo3000 opened a new pull request #60: IGNITE-10146 Refresh missing from Git
prs while full reindex
URL: https://github.com/apache/ignite-teamcity-bot/pull/60
This is an automated message from the Apache Git Service.
To
Vladimir,
We have a major IgniteSet improvement `Separate cache for non-collocated
IgniteSet.` [1] which is not mentioned yet.
Should we also include it to the release notes?
[1] https://issues.apache.org/jira/browse/IGNITE-7823
On Tue, 6 Nov 2018 at 16:50 Vladimir Ozerov wrote:
> Igniters,
Petr, some manual digest, is probably not needed because Apache list allows
subscribing to digest. dev-digest-subsr...@ignite.apache.org if I remember
this correctly.
вт, 6 нояб. 2018 г. в 18:28, Petr Ivanov :
> Can be Jira notifications united in some kind of daily digest?
> Maybe we can add
GitHub user ibessonov opened a pull request:
https://github.com/apache/ignite/pull/5316
IGNITE-10151 Fix BinaryMarshallerSelfTest#testDefaultMapping test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/5317
IGNITE-10150: Fixed handling of non-existing cache context in GridRedâ¦
â¦uceQueryExecutor.
You can merge this pull request into a Git repository by running:
$ git pull
53 matches
Mail list logo
