Re: Apache Ignite Site Changed its Face

The site and documentation is improved almost in per day basis. I spot the changes happened to the project on @dev and @user and adjust the materials and site to reflect them with the help of contributirs and committers who worked on a specific functionality. Don't see much sense to generate extra

Re: Apache Ignite Site Changed its Face

Looks great! "Keep calm and join the dark side" :-) 2017-07-28 19:54 GMT+03:00 Denis Magda : > Right, embrace the power of the dark side :) > > — > Denis > > > On Jul 28, 2017, at 1:22 AM, Sergey Kozlov wrote: > > > > Looks like we're going over the

[jira] [Created] (IGNITE-5875) Implement memory metric that will signal about uneven distribution of pages between segments of durable memory

Ivan Rakov created IGNITE-5875: -- Summary: Implement memory metric that will signal about uneven distribution of pages between segments of durable memory Key: IGNITE-5875 URL:

[jira] [Created] (IGNITE-5874) Store TTL expire times in B+ tree on per-partition basis

Ivan Rakov created IGNITE-5874: -- Summary: Store TTL expire times in B+ tree on per-partition basis Key: IGNITE-5874 URL: https://issues.apache.org/jira/browse/IGNITE-5874 Project: Ignite Issue

[jira] [Created] (IGNITE-5873) Zookeeper discovery does not work correctly when isolated clusters got deployed on similar hosts

MIKHAIL LIKHASHVA created IGNITE-5873: - Summary: Zookeeper discovery does not work correctly when isolated clusters got deployed on similar hosts Key: IGNITE-5873 URL:

Prepare works as it should work in JTA

Hi, guys. I've done IGNITE-4648, the idea was to improve prepare implementations, because async calls could hangs or fail if transaction state changes were not finished [1]. I modified internal transaction's prepare implementation, so now it wait for unfinished futures in transaction and added

Re: Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

> String encoding is a concept similar to "collation" in RDBMS. You can > define it either globally, or on per-table basis. Or on per-column (per-field) basis. Though Oracle does not have per-column charset, some other databases provide this option. MySQL: -

Re: Apache Ignite Site Changed its Face

Right, embrace the power of the dark side :) — Denis > On Jul 28, 2017, at 1:22 AM, Sergey Kozlov wrote: > > Looks like we're going over the dark side :-) > > On Fri, Jul 28, 2017 at 11:17 AM, Pavel Tupitsyn > wrote:

Re: Apache Ignite Site Changed its Face

That’s true, the site is not optimized for mobile and tablet screens. This will be improved in the nearest month. — Denis > On Jul 28, 2017, at 1:17 AM, Pavel Tupitsyn wrote: > > Looks great on desktop, but on mobile it is a disaster :( > > http://imgur.com/a/VIT1B

Re: [RESULT] [VOTE] Apache Ignite 2.1.0 Release (RC4)

Thanks Mauricio! Merged your patch. — Denis > On Jul 27, 2017, at 9:53 PM, Mauricio Stekl wrote: > > Hi Denis, > I have updated the “latest” reference to 2.1.0, and also updated canonical > metatags and GA code on all documentation .html files. > > Please apply the

[GitHub] ignite pull request #2363: ignite-1.8.9-p1

GitHub user asfedotov opened a pull request: https://github.com/apache/ignite/pull/2363 ignite-1.8.9-p1 for CI purposes only You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.8.9-p1 Alternatively

[GitHub] ignite pull request #2299: IGNITE-5753: Memory leak fixed

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/2299 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2354: IGNITE-5758: CPP: Added pointer semantics for pri...

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/2354 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2348: IGNITE-5771: Added Ignite::SetActive() for C++

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/2348 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2362: IGNITE-5621: Support BINARY and VARBINARY SQL typ...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2362 IGNITE-5621: Support BINARY and VARBINARY SQL types for C++ You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5621

[jira] [Created] (IGNITE-5872) Replace standard java maps for partition counters to more effective data structures

Alexey Goncharuk created IGNITE-5872: Summary: Replace standard java maps for partition counters to more effective data structures Key: IGNITE-5872 URL: https://issues.apache.org/jira/browse/IGNITE-5872

Re: Hello! IGNITE-5823

Hi Sergey, This ticket is unassigned. Feel free to assign it to yourself. Sincerely, Dmitry Pavlov пт, 28 июл. 2017 г. в 18:18, Серега Дорожкин : > Thank you! > > Can I pick this ticket (IGNITE-5823)? > > 2017-07-28 18:13 GMT+03:00 Alexey Goncharuk

Re: Hello! IGNITE-5823

Thank you! Can I pick this ticket (IGNITE-5823)? 2017-07-28 18:13 GMT+03:00 Alexey Goncharuk : > Sergey, > > Added you to the contributors list. > > 2017-07-28 18:02 GMT+03:00 Серега Дорожкин : > > > Yes, I need contributor access to Apache

Re: Hello! IGNITE-5823

Sergey, Added you to the contributors list. 2017-07-28 18:02 GMT+03:00 Серега Дорожкин : > Yes, I need contributor access to Apache JIRA. > Link to my JIRA account: > https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stalkxt > > 2017-07-28 17:41 GMT+03:00

Re: Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

Currently, marshaller determines the type of field (BYTE, INT, STRING etc.) only by the Class of data being serialized. It seems rather non-trivial to manage marshaling parameters at cache creation point. Alternatively, there exists simple and flexible way: just to introduce new Java type, say,

Re: Hello! IGNITE-5823

Yes, I need contributor access to Apache JIRA. Link to my JIRA account: https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stalkxt 2017-07-28 17:41 GMT+03:00 Dmitry Pavlov : > Hi Sergey, > > Welcome to the Ignite community! > > If you need contributor access to

Re: Plugins in tests

Pavel, I would create a new module just like "modules/extdata/p2p". --Yakov

[GitHub] ignite pull request #2361: Ignite 5793

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2361 Ignite 5793 PR fot test run. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5793 Alternatively you can review

Hello! IGNITE-5823

Hi, Igniters! I'm newbie here. I want to become a part of ignite community and as a first step I want to pick a simple ticket. For example, IGNITE-5823. I think, it's a best way to get to know the contribution process. What do you think about it? -- Best regards, Sergey.

Re: Apache Ignite Site Changed its Face

Looks great guys, kudos ! On Fri, Jul 28, 2017 at 1:22 PM Anton Vinogradov wrote: > Awesome! > > On Fri, Jul 28, 2017 at 11:22 AM, Sergey Kozlov > wrote: > >> Looks like we're *going over the dark side* :-) >> >> On Fri, Jul 28, 2017 at 11:17 AM,

[GitHub] ignite pull request #2360: Ignite 4908: not ready PR, only to discuss ideas

GitHub user SharplEr opened a pull request: https://github.com/apache/ignite/pull/2360 Ignite 4908: not ready PR, only to discuss ideas Not ready PR, only to discuss ideas. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-5871) IgniteCacheP2pUnmarshallingRebalanceErrorTest.testResponseMessageOnUnmarshallingFailed fails

Eduard Shangareev created IGNITE-5871: - Summary: IgniteCacheP2pUnmarshallingRebalanceErrorTest.testResponseMessageOnUnmarshallingFailed fails Key: IGNITE-5871 URL:

[jira] [Created] (IGNITE-5870) IgniteTopologyValidatorGridSplitCacheTest#testTopologyValidator fails

Eduard Shangareev created IGNITE-5870: - Summary: IgniteTopologyValidatorGridSplitCacheTest#testTopologyValidator fails Key: IGNITE-5870 URL: https://issues.apache.org/jira/browse/IGNITE-5870

[jira] [Created] (IGNITE-5869) Unexpected timeout exception while client connected with different BinaryConfiguration compactFooter param.

Stanilovsky Evgeny created IGNITE-5869: -- Summary: Unexpected timeout exception while client connected with different BinaryConfiguration compactFooter param. Key: IGNITE-5869 URL:

[jira] [Created] (IGNITE-5868) Fix Activate/Deactivate cluster suite for windows agents

Dmitriy Pavlov created IGNITE-5868: -- Summary: Fix Activate/Deactivate cluster suite for windows agents Key: IGNITE-5868 URL: https://issues.apache.org/jira/browse/IGNITE-5868 Project: Ignite

[jira] [Created] (IGNITE-5867) Web console: Add parameter for adding primary key columns to generated POJO class

Evgenii Zhuravlev created IGNITE-5867: - Summary: Web console: Add parameter for adding primary key columns to generated POJO class Key: IGNITE-5867 URL: https://issues.apache.org/jira/browse/IGNITE-5867

[GitHub] ignite pull request #2358: IGNITE-GG-12549 SQL: Add support for Java 8 Time ...

GitHub user asfedotov opened a pull request: https://github.com/apache/ignite/pull/2358 IGNITE-GG-12549 SQL: Add support for Java 8 Time API classes in date\time functions You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2349: IGNITE-4172 SQL: Add support for Java 8 Time API ...

Github user asfedotov closed the pull request at: https://github.com/apache/ignite/pull/2349 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Plugins in tests

TestPlatformPlugin is only needed for .NET tests. I would gladly move it somewhere else, just not sure how to do this properly, because .NET uses ignite-core only. Any advice? Create a new module? Pavel On Fri, Jul 28, 2017 at 2:57 PM, Yakov Zhdanov wrote: > Hello! > > I

[GitHub] ignite pull request #2357: IGNITE-5856: BLAS integration phase 1

GitHub user ybabak opened a pull request: https://github.com/apache/ignite/pull/2357 IGNITE-5856: BLAS integration phase 1 The first part of BLAS integration with Ignite ML. Current only gemm for local matrix multiply. You can merge this pull request into a Git repository by

Plugins in tests

Hello! I see this output in each test I run: [2017-07-28 14:43:58,648][INFO ][test-runner-#139%datastreamer.DataStreamProcessorSelfTest%][IgnitePluginProcessor] Configured plugins: [2017-07-28 14:43:58,648][INFO ][test-runner-#139%datastreamer.DataStreamProcessorSelfTest%][IgnitePluginProcessor]

[jira] [Created] (IGNITE-5866) JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails on master

Nikolay Izhikov created IGNITE-5866: --- Summary: JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails on master Key: IGNITE-5866 URL: https://issues.apache.org/jira/browse/IGNITE-5866

Re: BinaryObjectBuilder: policy of reusing

Let's just fix this bug and allow BinaryObjectBuilder re-use. On Thu, Jul 27, 2017 at 11:43 AM, Dmitriy Setrakyan wrote: > On Thu, Jul 27, 2017 at 3:14 AM, Pavel Tupitsyn > wrote: > > > BinaryObjectBuilder reuse should be allowed, performance is an

Re: Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

String encoding is a concept similar to "collation" in RDBMS. You can define it either globally, or on per-table basis. The same should be done for Ignite. We do not define behavior of a type. We define behavior of a *storage*. Two cases when proposed approach with per-type and per-type-field

Re: Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

> As Pavel mentioned, Marshaller should not be tied to cache > should be added to per-cache level Not sure if I follow. Marshalling and caching are two separate mechanisms. Defining binary format in CacheConfiguration violates separation of concerns. > Encoding *must not* be added to per-class or

Re: Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

Encoding *must not* be added to per-class or per-field level, this is wrong. It should be added to per-cache level, and to per-cache-column level in future. пт, 28 июля 2017 г. в 14:27, Andrey Kuznetsov : > We discussed this with Pavel and Anton just a moment ago. Summary

Re: Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

We discussed this with Pavel and Anton just a moment ago. Summary follows. - New byte "flag" is to be added (ENCODED_STRING) - 'Encoding' property is to be added at -- global level (BinaryConfiguration) -- per-class level (BinaryTypeConfiguration) -- per-field level

Re: Assertions as binary data validation checks in deserialization

We have a lot of such assertions. They are created for developers, not for users. We cannot cover all such places with checks for corrupted data or so, as it will decrease performance significantly. Hence, proposed fix doesn't make sense to me. чт, 27 июля 2017 г. в 23:43, Andrey Kuznetsov

Re: Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

As Pavel mentioned, Marshaller should not be tied to cache, BinaryObject should be self-explanatory, i.e. containing all information necessary for unmarshalling. This is an absolute requirement. We will have one extra byte for in serialized form, meaning that advantage of custom encoding will

[jira] [Created] (IGNITE-5865) TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing

Pavel Kovalenko created IGNITE-5865: --- Summary: TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing Key: IGNITE-5865 URL: https://issues.apache.org/jira/browse/IGNITE-5865 Project:

Re: Apache Ignite Site Changed its Face

Looks like we're *going over the dark side* :-) On Fri, Jul 28, 2017 at 11:17 AM, Pavel Tupitsyn wrote: > Looks great on desktop, but on mobile it is a disaster :( > > http://imgur.com/a/VIT1B > > > > On Fri, Jul 28, 2017 at 11:05 AM, Yakov Zhdanov >

[jira] [Created] (IGNITE-5863) Implement common component to show item selected for table

Dmitriy Shabalin created IGNITE-5863: Summary: Implement common component to show item selected for table Key: IGNITE-5863 URL: https://issues.apache.org/jira/browse/IGNITE-5863 Project: Ignite

Re: Apache Ignite Site Changed its Face

I like the new design. Looks good! --Yakov

[jira] [Created] (IGNITE-5862) PlatformMessageParser & PlatformRequestHandler

Pavel Tupitsyn created IGNITE-5862: -- Summary: PlatformMessageParser & PlatformRequestHandler Key: IGNITE-5862 URL: https://issues.apache.org/jira/browse/IGNITE-5862 Project: Ignite Issue

[jira] [Created] (IGNITE-5861) Basic cache operations

Pavel Tupitsyn created IGNITE-5861: -- Summary: Basic cache operations Key: IGNITE-5861 URL: https://issues.apache.org/jira/browse/IGNITE-5861 Project: Ignite Issue Type: Sub-task

[GitHub] ignite pull request #2352: IGNITE-5769 Abstract away .NET->Java calls

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2352 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is