Nikolay,
Actually 4 "+1" binding.
You did not count my "+1".
:)
On Tue, Dec 4, 2018 at 4:28 AM Nikolay Izhikov wrote:
> Igniters,
>
> Apache Ignite 2.7.0 release (RC2) has been accepted.
>
> 3 "+1" binding votes received:
>
> - Pavel Tupitsyn
> - Dmitriy Pavlov
> - Nikolay Izhikov
>
> Vote
GitHub user voropava opened a pull request:
https://github.com/apache/ignite/pull/5563
IGNITE-10511 removeExplicitNodeLocks() removed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10511
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5564
IGNITE-10461: Create Mvcc PDS test suite.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10461
Sorry, Alex.
I miss your +1.
Thank you, very much for checking RC artifacts.
вт, 4 дек. 2018 г., 7:10 Alexey Kuznetsov akuznet...@apache.org:
> Nikolay,
>
> Actually 4 "+1" binding.
>
> You did not count my "+1".
>
> :)
>
>
> On Tue, Dec 4, 2018 at 4:28 AM Nikolay Izhikov
> wrote:
>
> >
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5554
IGNITE-10483: Fix marshaller failures handling for mvcc Enlist requests.
You can merge this pull request into a Git repository by running:
$ git pull
+1
I've downloaded and built the sources, run several examples.
Also, I checked several times the test
`testAtomicOnheapTwoBackupAsyncFullSync` related to the issue
discussed in a separated thread - OK.
On Sun, Dec 2, 2018 at 11:26 PM Dmitriy Pavlov wrote:
>
> +1 binding
>
> I've checked new RC
dspavlov commented on a change in pull request #86: IGNITE-10071 Queued and
running builds hang in the TC bot
URL: https://github.com/apache/ignite-teamcity-bot/pull/86#discussion_r238243619
##
File path:
Igor, Vladimir, Ivan,
perhaps, we are focused too much on update counters. This feature was
designed for the continuous queries and it may not be suited well for
the historical rebalance. What if we would track updates on
per-transaction basis instead of per-update basis? Let's consider two
Hi Oleg,
I noticed that GridAbstractTest is now capable to run junit4 tests.
What are the current recommendations for writing new tests? Can we use
junit4 annotation for new tests?
пн, 12 нояб. 2018 г. в 19:58, oignatenko :
>
> Hi Ivan,
>
> I am currently testing approach you used in pull/5354 in
Confirming. Test never failed in AI 2.7 even though it contains mentioned
MVCC commit.
On Mon, Dec 3, 2018 at 1:36 PM Vyacheslav Daradur
wrote:
> Guys, I checked that `testAtomicOnheapTwoBackupAsyncFullSync` failed
> in the master (as described Ivan), but it passes in branch ignite-2.7
> (tag
Nikolay,
I think that end-user may face the problem during call IgniteCache#invoke
on a cache with registered continious query if cache's configuration is as
in the failed test: [PARTITIONED, ATOMIC, FULL_SYNCH, 2 backups].
I've found that failure has been introduced by MVCC commit [1]. As I
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4663
---
SomeFire commented on a change in pull request #86: IGNITE-10071 Queued and
running builds hang in the TC bot
URL: https://github.com/apache/ignite-teamcity-bot/pull/86#discussion_r238206522
##
File path:
SomeFire commented on a change in pull request #86: IGNITE-10071 Queued and
running builds hang in the TC bot
URL: https://github.com/apache/ignite-teamcity-bot/pull/86#discussion_r238204941
##
File path: build.gradle
##
@@ -41,6 +41,7 @@ allprojects {
ext {
Roman,
We already track updates on per-transaction basis. The only difference is
that instead of doing a single "increment(1)" for transaction we do
"increment(X)" where X is number of updates in the given transaction.
On Mon, Dec 3, 2018 at 1:16 PM Roman Kondakov
wrote:
> Igor, Vladimir,
Hi Ivan, Vladimir,
@Ivan
> 1. According to the jdbc spec [1] setNetworkTimeout method is
> optional. What user problem we are going to solve by implementing that
> method?
>
We are going to give user an ability to set custom connection timeout.
> Also I checked another quite popular jdbc driver
Guys, I checked that `testAtomicOnheapTwoBackupAsyncFullSync` failed
in the master (as described Ivan), but it passes in branch ignite-2.7
(tag 2.7.0-rc2), so this shouldn't block the release.
Ivan, were you able to reproduce this issue in ignite-2.7 branch?
On Mon, Dec 3, 2018 at 1:03 PM Ivan
Hi,
This is better to be asked on the dev-list – added that to the To, and Bcc’ed
user-list.
I actually don’t think you can run tests for a specific module – either a
single test, or a single test suite, or all of them.
I would usually either run a single test from IDEA or run all tests via
Sergey Antonov created IGNITE-10507:
---
Summary: VisorIdleVerifyTask should return exceptions from all
nodes if they are occured
Key: IGNITE-10507
URL: https://issues.apache.org/jira/browse/IGNITE-10507
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5556
IGNITE-10368: Add mvcc cache test suite 9.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10368
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/5525
---
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/
IGNITE-10509 reordered setting of timeout flag and transaction state
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Dmitriy Govorukhin created IGNITE-10508:
---
Summary: Need to support the new checkpoint feature not wait for
the previous operation to complete
Key: IGNITE-10508
URL:
SomeFire commented on a change in pull request #86: IGNITE-10071 Queued and
running builds hang in the TC bot
URL: https://github.com/apache/ignite-teamcity-bot/pull/86#discussion_r238206934
##
File path:
Vladimir,
the difference between per-transaction basis and update-counters basis
is the fact that at the first update we don't know the actual update
counter of this update - we just count deltas on enlist phase. Actual
update counter of this update will be assigned on transaction commit.
Roman,
What is the advantage of your algorithm compared to previous one? Previous
algorithm does almost the same, but without updating two separate counters,
and looks simpler to me. Only one update is sufficient - at transaction
commit. When transaction starts we just read currently active
Stanislav Lukyanov created IGNITE-10506:
---
Summary: Emphasize the need to close the query cursors in docs
Key: IGNITE-10506
URL: https://issues.apache.org/jira/browse/IGNITE-10506
Project: Ignite
Anton Kalashnikov created IGNITE-10509:
--
Summary: Rollback exception instead of timeout exception
Key: IGNITE-10509
URL: https://issues.apache.org/jira/browse/IGNITE-10509
Project: Ignite
Yury Babak created IGNITE-10510:
---
Summary: [ML] Use OneVsRest for
SVMLinearMultiClassClassificationTrainer
Key: IGNITE-10510
URL: https://issues.apache.org/jira/browse/IGNITE-10510
Project: Ignite
Pavel Voronkin created IGNITE-10511:
---
Summary: disco-event-worker can be deadlocked by
BinaryContext.metadata running is sys striped pool waiting for cache entry lock
Key: IGNITE-10511
URL:
Andrew Mashenkov created IGNITE-10512:
-
Summary: Fix javadoc for public Query classes.
Key: IGNITE-10512
URL: https://issues.apache.org/jira/browse/IGNITE-10512
Project: Ignite
Issue
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5531
---
asfgit closed pull request #85: IGNITE-10436 Add ticket and PR links on report
TC Bot page
URL: https://github.com/apache/ignite-teamcity-bot/pull/85
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5540
---
GitHub user laz2 opened a pull request:
https://github.com/apache/ignite/pull/5557
IGNITE-10513 Fix NullPointerException on reconnect
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/laz2/ignite ignite-10513
Alternatively you
Dmitry Lazurkin created IGNITE-10513:
Summary: Java client stucks when connects to server with slow disk
Key: IGNITE-10513
URL: https://issues.apache.org/jira/browse/IGNITE-10513
Project: Ignite
asfgit closed pull request #86: IGNITE-10071 Queued and running builds hang in
the TC bot
URL: https://github.com/apache/ignite-teamcity-bot/pull/86
This is an automated message from the Apache Git Service.
To respond to
Vyacheslav, thank you for remark. I've tried to launch test on the 2.7
version and it is fine.
I changed priority of the ticket from "Blocker" to "Major" and fix version
to 2.8.
пн, 3 дек. 2018 г. в 13:53, Vladimir Ozerov :
> Confirming. Test never failed in AI 2.7 even though it contains
GitHub user sk0x50 opened a pull request:
https://github.com/apache/ignite/pull/5558
IGNITE-10514: Cache validation on the primary node may result in
AssertionError
You can merge this pull request into a Git repository by running:
$ git pull
Ilya Kasnacheev created IGNITE-10515:
Summary: In JDBC thick driver streaming mode, INSERTs ignored
silently when trying to insert into wrong table
Key: IGNITE-10515
URL:
Vyacheslav Koptilin created IGNITE-10514:
Summary: Cache validation on the primary node may result in
AssertionError
Key: IGNITE-10514
URL: https://issues.apache.org/jira/browse/IGNITE-10514
Igniters,
Apache Ignite 2.7.0 release (RC2) has been accepted.
3 "+1" binding votes received:
- Pavel Tupitsyn
- Dmitriy Pavlov
- Nikolay Izhikov
Vote thread:
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html
signature.asc
Description: This
GitHub user zaleslaw opened a pull request:
https://github.com/apache/ignite/pull/5559
IGNITE-10380: Drop Multi-label Classification for LogReg and SVM
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Hello Ignite Community!
My name is Vladimir. I want to contribute to Apache Ignite, my JIRA username is
"Vladimir Pligin".
Thanks!
Hi Vladimir,
Welcome to the Apache Software Foundation and to the Apache Ignite
Community.
I've added your account to the list of contributors. Now you should be able
to assign an issue to yourself.
Should you have any questions please do not hesitate to ask here. Looking
forward to your
Stanislav Lukyanov created IGNITE-10516:
---
Summary: Storage is corrupted after CREATE INDEX IF NOT EXISTS on
different tables
Key: IGNITE-10516
URL: https://issues.apache.org/jira/browse/IGNITE-10516
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/5561
IGNITE-10406 .NET: Reset writer structures on reconnect
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-10406
Hi,
Have someone tried to investigate the issue related to Inspection TC task
execution time variation (from 0.5 up to 1,5 hours)?
Can we enable GC logs for this task or may be even get CPU, Disk, Network
metrics?
Can someone check if there are unnecessary Idea plugins starts that can be
safely
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/5560
IGNITE-10516: Storage is corrupted after CREATE INDEX IF NOT EXISTS on
different tables
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user oignatenko opened a pull request:
https://github.com/apache/ignite/pull/5562
IGNITE-10175 migrate core module tests from Junit 3 to 4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5448
---
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/5552
IGNITE-10491 added test to investigate max threads
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10491
Github user dgovorukhin closed the pull request at:
https://github.com/apache/ignite/pull/5457
---
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/5553
IGNITE-10205 add to utility command - ./control.sh --cache idle_verifâ¦
â¦y --dump abbility to exclude cache from output file
You can merge this pull request into a Git repository by running:
Ivan, please, clarify.
How your investigation are related to 2.7 release?
Do you think it's a release blocker?
If yes, please, describe impact to users and how users can reproduce this
issue.
пн, 3 дек. 2018 г., 9:30 Ivan Fedotov ivanan...@gmail.com:
> I've created the PR
ARomantsov created IGNITE-10504:
---
Summary: If client have cache resource with not configurate data
region it stop by handler
Key: IGNITE-10504
URL: https://issues.apache.org/jira/browse/IGNITE-10504
56 matches
Mail list logo
