GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/3601
gg-13377 : Fixed error handling for corrupted page store.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Ilya Kasnacheev created IGNITE-7881:
---
Summary: Add tests for using TreeMap/TreeSet in cache key
Key: IGNITE-7881
URL: https://issues.apache.org/jira/browse/IGNITE-7881
Project: Ignite
Mikhail Cherkasov created IGNITE-7880:
-
Summary: Enum values not shown correctly in Webconsole
Key: IGNITE-7880
URL: https://issues.apache.org/jira/browse/IGNITE-7880
Project: Ignite
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/3600
IGNITE-7860 JDBC thin driver: set default socket buffer sizes to 64Kb
You can merge this pull request into a Git repository by running:
$ git pull
Hello, Ilya.
> I think it's time to end this, if that was the case. DataStreamer should
> not be a special case and it should guarantee data safety. WDYT?
+1 from me.
I'm also facing this issue.
Ticket - https://issues.apache.org/jira/browse/IGNITE-7756
Discussion -
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/3602
IGNITE-7881 Tests for using TreeMap or TreeSet as cache key.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7881
Dear Igniters, why do I have a hunch that DataStreamer would readily
swallow exceptions?
DataStreamerImpl:1756 swallows marshalling error, lines 1774 & 1781 eat
deployment errors.
Some people are worried they can fill a leaking vessel without noticing
anything off.
Also in line 2156 fsync() on
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/3603
IGNITE-7882 Always use topology mapping for atomic updates.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7882
Hi Vyacheslav,
It is possible to use lambdas in test code and node local-only code (e.g.
checkpointing, page memory, etc).
In other words any other classes, which are transferred/may be trasnferred
into network, can't use lambdas.
There is also recommendation to avoid mass change of anonymous
Hi Vyacheslav,
I would not recommend using them without strong reasons. While convenient
for developers in general, some of these features has hidden pitfails,
which may affect performance and serialization. But as our product is very
performance sensitive, it is better to have slightly more code
Hi Pavel, Igniters,
There is new TC failure from .NET tests. Issue link:
https://issues.apache.org/jira/browse/IGNITE-7878
Thanks to V.Ozerov we have located it is because usage
of TcpDiscoveryMulticastIpFinder. Probably there is some other Ignite node
running on other agents. Folks from
Hi, Igniters!
Since we official support Java 8, I want to find out the following question:
Are there any restrictions on using lambdas and other Java 8 features?
--
Best Regards, Vyacheslav D.
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/3604
ignite-6643-2.1Marshalling improvements (backport)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-6643-2.1
By the way, usage of lambdas instead of anonymous class may have positive
performance effect.
And Java 8 provides us a number of new features, which allows Ignite
operate faster (e.g. Arrays.parrallelSort, list.sort(), etc).
пн, 5 мар. 2018 г. в 18:15, Vladimir Ozerov :
>
Hi Igniters,
There is a job on Apache Jenkins for nightly builds of Ignite [1],
which was useful for providing fast fixes to our users. However,
it seems that noone supports it any more as the last successfull
build date is 31.05.2017.
Does anyone know what is the issue with the job and why it
Dmitry, I saw them, but it looks like just randomness.
I've checked it locally several times.
They failed only in one TeamCity's build of four.
Started build once again to be sure.
On Mon, Mar 5, 2018 at 6:59 PM, Dmitry Pavlov wrote:
> I can see Nikolay Izhikov as
Mikhail Cherkasov created IGNITE-7883:
-
Summary: Cluster can have inconsistent affinity configuration
Key: IGNITE-7883
URL: https://issues.apache.org/jira/browse/IGNITE-7883
Project: Ignite
Hi Igor,
This build did not make much sense anyway:
1) (At least) platform artifacts (.NET) can't be built there, so the
package is incomplete
2) We have TeamCity, why duplicate maintenance efforts?
Nightly release builds are very useful, but they should be done on TeamCity.
(We have them for
I can see Nikolay Izhikov as reviewer in Upsource.
Nikolay, would you run review first?
I've found several suspicious tests : Test fail rate is less than 1%, it is
probably new failure
IgniteCacheTestSuite2:
GridCachePartitionedTxSingleThreadedSelfTest.testOptimisticReadCommittedRollback
(fail
I've done some test-builds iteration on the weekends.
Tests [1] look well.
Does anyone have time to do the final review [2][3] and merge it?
[1] https://ci.ignite.apache.org/viewLog.html?buildId=1125676
[2] https://github.com/apache/ignite/pull/3578
[3]
Hi Pavel,
Thank you!
Let's wait for fix at TeamCity.
Sincerely,
Dmitriy Pavlov
пн, 5 мар. 2018 г. в 19:09, Pavel Tupitsyn :
> Hi Dmitry,
>
> This test has been there forever. It checks that Ignite can start with
> default config.
> I think this is quite useful. TeamCity
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/3605
ignite-6643-2.3 Marshalling improvements
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-6643-2.3
Alternatively
Hi Igniters!
I’d like to do next step in our data compression discussion [1].
Most Igniters vote for per-data-page compression.
I’d like to accumulate main theses to start implementation:
- page will be compressed with the dictionary-based approach (e.g.LZV)
- page will be compressed in batch
Igniters,
We have uploaded a 2.4.0 release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.4.0-rc1/
Git tag name is
2.4.0-rc1
This release includes the following changes:
Ignite:
* Introduced Baseline Affinity Topology
* Ability to disable WAL for cache in runtime through
Dmitry, Vladimir, thank you for the clarification!
On Mon, Mar 5, 2018 at 6:23 PM, Dmitry Pavlov wrote:
> By the way, usage of lambdas instead of anonymous class may have positive
> performance effect.
>
> And Java 8 provides us a number of new features, which allows
Ilya,
IgniteDataStreamer#addData method returns future which should be completed
with error if one is thrown on server side. Does this happen or not?
-Val
On Mon, Mar 5, 2018 at 4:10 AM, Nikolay Izhikov wrote:
> Hello, Ilya.
>
> > I think it's time to end this, if that
Pavel Kovalenko created IGNITE-7882:
---
Summary: Atomic update requests should always use topology
mappings instead of affinity
Key: IGNITE-7882
URL: https://issues.apache.org/jira/browse/IGNITE-7882
In C++ there are no tests that use TcpDiscoveryMulticastIpFinder. There
are examples, though, that use it. As far as I know, currently all examples
use TcpDiscoveryMulticastIpFinder, and there were some objections
against using VmIpFinder instead.
Am I right, folks?
Best Regards,
Igor
On Mon,
Hi, Denis, Igniters,
I've updated the report for the last weekend mass run-all, please find it
in wiki
https://cwiki.apache.org/confluence/pages/viewpageattachments.action?pageId=73631266
In 30 clean runs, there was 371 failed tests, 21 suites. During previous
mass run there were 804 tests
Denis Magda created IGNITE-7884:
---
Summary: Ship SQL scripts with same database in Ignite
Key: IGNITE-7884
URL: https://issues.apache.org/jira/browse/IGNITE-7884
Project: Ignite
Issue Type: New
The vote passed by lazy consensus :) Here is a ticket:
https://issues.apache.org/jira/browse/IGNITE-7884
Vladimir, look forward to co-operating with you on that task.
--
Denis
On Mon, Feb 26, 2018 at 4:49 PM, Denis Magda wrote:
> Igniters,
>
> To demonstrate Ignite SQL
Prachi Garg created IGNITE-7885:
---
Summary: Error on Baseline page on Web Console
Key: IGNITE-7885
URL: https://issues.apache.org/jira/browse/IGNITE-7885
Project: Ignite
Issue Type: Bug
Astonishing progress! Thanks for keep driving this activity and making the
project more and more reliable.
--
Denis
On Mon, Mar 5, 2018 at 1:47 PM, Dmitry Pavlov wrote:
> Hi, Denis, Igniters,
>
> I've updated the report for the last weekend mass run-all, please find it
>
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/3531
---
Hi Igniters,
I noticed that I'm not mentioned on the community contributors page:
https://ignite.apache.org/community/resources.html
Perhaps there is someone else, who is not yet added. Or information is not
up-to-date.
Please check the data for yourself and respond if you need to be added / or
Hi Dmitriy,
Thanks for kicking off the discussion. I'll wait for a couple of days for
other response and update the page in bulk.
--
Denis
On Mon, Mar 5, 2018 at 12:32 PM, Dmitry Pavlov
wrote:
> Hi Igniters,
>
> I noticed that I'm not mentioned on the community
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/3525
---
Igniters,
Do we comply with the next release requirements? Vladimir as a 2.4 release
manager, could you double check that we are in a good state?
--
Denis
-- Forwarded message --
From: Henk P. Penning
Date: Mon, Mar 5, 2018 at 3:18 AM
Subject: checksum file
Prachi Garg created IGNITE-7886:
---
Summary: Provide a list of node Ids on the Baseline page on Web
Console
Key: IGNITE-7886
URL: https://issues.apache.org/jira/browse/IGNITE-7886
Project: Ignite
Nikolay, what's your Wiki ID? I'll grant you required permissions.
--
Denis
On Sun, Mar 4, 2018 at 11:00 PM, Nikolay Izhikov
wrote:
> Hello, Denis.
>
> > I would encourage you creating an IEP
>
> That is exactly what we want to do :)
>
> But seems I have not sufficient
Thank you, it's - nizhikov
В Пн, 05/03/2018 в 15:09 -0800, Denis Magda пишет:
> Nikolay, what's your Wiki ID? I'll grant you required permissions.
>
> --
> Denis
>
> On Sun, Mar 4, 2018 at 11:00 PM, Nikolay Izhikov wrote:
> > Hello, Denis.
> >
> > > I would encourage you
On Mon, Mar 5, 2018 at 12:57 PM, Denis Magda wrote:
> Igniters,
>
> Do we comply with the next release requirements? Vladimir as a 2.4 release
> manager, could you double check that we are in a good state?
>
I think we do. We only provide SHA files for our releases.
+1
Checked Ignite.NET:
* Build from sources
* Download binaries and run examples
* Build NuGet packages on TeamCity [1] and test them
[1] https://ci.ignite.apache.org/viewLog.html?buildId=1126956
On Mon, Mar 5, 2018 at 10:42 PM, Vladimir Ozerov
wrote:
> Igniters,
>
> We
On Mon, Mar 5, 2018 at 7:58 AM, Pavel Tupitsyn wrote:
> Hi Igor,
>
> This build did not make much sense anyway:
> 1) (At least) platform artifacts (.NET) can't be built there, so the
> package is incomplete
> 2) We have TeamCity, why duplicate maintenance efforts?
>
What
Regarding release notes:
1. No changes in Ignite.C++?
2. > Fixed output of big numbers in SQL query results
Are we including trivial bugfixes now?
On Tue, Mar 6, 2018 at 10:26 AM, Pavel Tupitsyn
wrote:
> +1
>
> Checked Ignite.NET:
> * Build from sources
> * Download
45 matches
Mail list logo