[jira] [Created] (IGNITE-5838) The IgniteCache.loadCacheAsync method is not executed asynchronously.

Yujue Li created IGNITE-5838: Summary: The IgniteCache.loadCacheAsync method is not executed asynchronously. Key: IGNITE-5838 URL: https://issues.apache.org/jira/browse/IGNITE-5838 Project: Ignite

Re: Cache Metrics

Andrey, I would simply take an average if a mixed clients-servers cluster group is used. In general, the goal of the ticket was to fix the time-based metrics on the server side. As far as I understand they are already calculated properly on the client’s considering network contribution, right?

Re: [VOTE] Apache Ignite 2.1.0 RC4

+1 (non-binding) -- Roman On Monday, July 24, 2017 10:32 PM, Anton Vinogradov wrote: Igniters, This vote based on same files as RC3. Only one change is that I signed zips with my signature. KEYS files (https://dist.apache.org/repos/dist/release/ignite/KEYS) was

Re: [VOTE] Apache Ignite 2.1.0 RC4

+1 (non-binding) On Wed, Jul 26, 2017 at 12:35 AM, Konstantin Boudnik wrote: > +1 [binding] > > - Checked the signature > - Checked the sha1 > - Successfully ran the build > - RAT is clean > > Things that need to be improved in the next release: > - neither sha1 nor md5 are

[GitHub] ignite pull request #2345: IGNITE-5837 Test logic fix.

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2345 IGNITE-5837 Test logic fix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5837 Alternatively you can

[GitHub] ignite pull request #2344: IGNITE-5572

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2344 IGNITE-5572 ALTER TABLE ADD COLUMN You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5572 Alternatively you

[jira] [Created] (IGNITE-5837) Fix logic in DynamicIndexAbstractConcurrentSelfTest

Alexander Paschenko created IGNITE-5837: --- Summary: Fix logic in DynamicIndexAbstractConcurrentSelfTest Key: IGNITE-5837 URL: https://issues.apache.org/jira/browse/IGNITE-5837 Project: Ignite

Re: [VOTE] Apache Ignite 2.1.0 RC4

+1 [binding] - Checked the signature - Checked the sha1 - Successfully ran the build - RAT is clean Things that need to be improved in the next release: - neither sha1 nor md5 are trustful checksum'ing methods and aren't guaranteeing the authenticity of the source archive. We should be

Re: Resurrect FairAffinityFunction

Create a ticket: https://issues.apache.org/jira/browse/IGNITE-5836 -Val On Tue, Jul 25, 2017 at 11:54 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Semyon, > > We had some improvements, but to knowledge fair affinity still provides > much better distribution (at least I

[jira] [Created] (IGNITE-5836) AffinityFunctionContext should provide consistent previous assignment

Valentin Kulichenko created IGNITE-5836: --- Summary: AffinityFunctionContext should provide consistent previous assignment Key: IGNITE-5836 URL: https://issues.apache.org/jira/browse/IGNITE-5836

Re: .Net client call tx,close in other thread

Pavel. You will fix .Net client so I don't need to change threadId checks in my pull request. Is that correct? 25.07.2017 20:19, Pavel Tupitsyn пишет: Further investigation shows that platform code performs unnecessary close() calls for committed & rolled back transactions (sync and async).

Re: Changing public IgniteCompute API to improve changes in 5037 ticket

Alexey, Is there exact use case that is currently not supported? I really would like to see one, because such a big API change should add clear value. ComputeGrid is not used very often, and so far I've never seen any questions from users about using it in conjunction with affinity collocation.

Re: Changing public IgniteCompute API to improve changes in 5037 ticket

Anton, How does topology change break this functionality? Closures executed with affinityRun/Call fail over in the same way as any ComputeJob. -Val On Tue, Jul 25, 2017 at 5:48 AM, Anton Vinogradov wrote: > Alexei, > > > How would task know the partition it is

Re: Resurrect FairAffinityFunction

Semyon, We had some improvements, but to knowledge fair affinity still provides much better distribution (at least I haven't seen any results showing otherwise). Please correct me if I'm wrong. Actually, I think it's not an issue with fair function in particular, but rather a design flow in

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

On Tue, Jul 25, 2017 at 12:36 PM, Vladimir Ozerov wrote: > Vyacheslav, > When we finish varlen optimization for string lengths, I am afraid we could > end up with very messy protocol, should we mix encoded length and encoding. > > Dima, > Encoding must be set on per field

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

Vladimir, Thanks for reply. In any case, we'll break compatibility by introducing new feature in marshalling. But both approaches preserve backward compatibility. I deemed it's unusual to make two differerent type markers (flags) for single datatype. I can't see the source right now, but I'm

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

Vyacheslav, When we finish varlen optimization for string lengths, I am afraid we could end up with very messy protocol, should we mix encoded length and encoding. Dima, Encoding must be set on per field basis. This will give us as most flexible solution at the cost of 1-byte overhead. вт, 25

[GitHub] ignite pull request #2123: IGNITE-5278: First stage of BLAS (Local onheap st...

Github user artemmalykh closed the pull request at: https://github.com/apache/ignite/pull/2123 --- 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

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

I don't understand why this encoding is done on per-object and not on per-cache level. Shouldn't the column-to-encoding mapping be defined at cache level configuration? On Tue, Jul 25, 2017 at 12:13 PM, Vladimir Ozerov wrote: > Andrey, > > You cannot have optional part in

Re: .Net client call tx,close in other thread

Further investigation shows that platform code performs unnecessary close() calls for committed & rolled back transactions (sync and async). Ticket filed: https://issues.apache.org/jira/browse/IGNITE-5834 I'll fix this tomorrow and it should resolve your issue. Thanks, Pavel On Tue, Jul 25,

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

Hi Andrey. Sound very useful. We can save one byte if will use controlled overflow on [nonNegativeIntStrLen]: If [nonNegativeIntStrLen < 0] then [string is encoded] I have some questions: Will there any public API, e.g. "Encoder" interace? Will user have the opportunity to define own encoding

[jira] [Created] (IGNITE-5835) Implement highlight item in non-multiple dropdown

Dmitriy Shabalin created IGNITE-5835: Summary: Implement highlight item in non-multiple dropdown Key: IGNITE-5835 URL: https://issues.apache.org/jira/browse/IGNITE-5835 Project: Ignite

[jira] [Created] (IGNITE-5834) .NET: Do not close transaction on async commit/rollback

Pavel Tupitsyn created IGNITE-5834: -- Summary: .NET: Do not close transaction on async commit/rollback Key: IGNITE-5834 URL: https://issues.apache.org/jira/browse/IGNITE-5834 Project: Ignite

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

Andrey, You cannot have optional part in the middle as it will break compatibility in dangerous way, probably leading to node crash. Also having INT (4 bytes) looks too much for me. Instead, I would add new type "encoded string": 1 byte - type 1 byte - encoding code, map frequently used

Re: .Net client call tx,close in other thread

Anyway, disallowing close() from another thread would be a breaking change, we can't do that. On Tue, Jul 25, 2017 at 7:36 PM, Pavel Tupitsyn wrote: > I've reproduced the issue, it happens because in .NET we auto-close the > transaction > on commit/rollback. This involves

[GitHub] ignite pull request #2343: Ignite 1.9.5

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2343 Ignite 1.9.5 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.9.5 Alternatively you can review and apply

[GitHub] ignite pull request #2342: for-dotNET-tests-ignite-5712

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/2342 for-dotNET-tests-ignite-5712 You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-5712-test Alternatively you can review

Re: .Net client call tx,close in other thread

I've reproduced the issue, it happens because in .NET we auto-close the transaction on commit/rollback. This involves two things: * release .NET reference to Java object * call Transaction.close() With sync methods this is trivial, but with commitAsync/rollbackAsync we have to call close() in

Meetup/Live Streaming: An Intro to Ignite

Igniters, If you live in London or close to it, stop by the meetup Akmal is giving there tomorrow: https://ignite.apache.org/events.html#Brighton-Java-241395191 Rest of us can grasp an opportunity of the live streaming. Find the link on this page:

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

I apologize for damaged formatting. Below is my message as it should be. Hi Igniters, I'd like to discuss future changes related to https://issues.apache.org/ jira/browse/IGNITE-5655. Is it really good idea to introduce new flag (ENCODED_STRING) for existing String datatype? It's possible to

Re: .Net client call tx,close in other thread

Hi, Pavel You can check my pull request. https://github.com/apache/ignite/pull/2334 For now I return checks so it has to fail on .Net test suite 2017-07-25 17:16 GMT+03:00 Pavel Tupitsyn : > Hi Николай, > > .NET test in question (TestTxStateAndExceptions) does not do any

[jira] [Created] (IGNITE-5833) Changing maven goal from "install" to "package" for building from sources

Oleg Ostanin created IGNITE-5833: Summary: Changing maven goal from "install" to "package" for building from sources Key: IGNITE-5833 URL: https://issues.apache.org/jira/browse/IGNITE-5833 Project:

[jira] [Created] (IGNITE-5832) .NET: Support transaction continuation in another thread

Pavel Tupitsyn created IGNITE-5832: -- Summary: .NET: Support transaction continuation in another thread Key: IGNITE-5832 URL: https://issues.apache.org/jira/browse/IGNITE-5832 Project: Ignite

[jira] [Created] (IGNITE-5831) .NET: Support TransactionScopeAsyncFlowOption.Enabled in TransactionScope

Pavel Tupitsyn created IGNITE-5831: -- Summary: .NET: Support TransactionScopeAsyncFlowOption.Enabled in TransactionScope Key: IGNITE-5831 URL: https://issues.apache.org/jira/browse/IGNITE-5831

Re: .Net client call tx,close in other thread

Hi Николай, .NET test in question (TestTxStateAndExceptions) does not do any multithreading, everything is called from a single thread. I see that the latest .NET run of your pull request on TeamCity finished successfully: http://ci.ignite.apache.org/viewLog.html?buildId=738277 Do you still

[jira] [Created] (IGNITE-5830) Introduce cache start & stop order on cluster activation

Pavel Kovalenko created IGNITE-5830: --- Summary: Introduce cache start & stop order on cluster activation Key: IGNITE-5830 URL: https://issues.apache.org/jira/browse/IGNITE-5830 Project: Ignite

Re: Cache Metrics

Den, doesn't make sense from my point if view. And we create new problem: how should we aggregate this metrics when user requests metrics for cluster group. On Mon, Jul 24, 2017 at 8:48 PM, Denis Magda wrote: > Guys, > > What if we calculate it on both sides? The client will

.Net client call tx,close in other thread

Hello, Igniters. I working on issue https://issues.apache.org/jira/browse/IGNITE-5712 I found that .Net client perform transaction operation(`tx.close()`) in thread that not owns transaction. So I can't include checks for threadId in my pull request. Is it a bug or a desirable behabiour? With

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

Hi Igniters,I'd like to discuss future changes related to IGNITE-5655 . Is it really good idea to introduce new flag (ENCODED_STRING) for existing String datatype? It's possible to use existing STRING flag at negligible performance cost.

Re: Disabling assertions in tests.

Vitaly, Assertions are made to ensure that Igntie works correctly internally. It seems rather strange that you need to break Ignite in order to test this ticket. It may be an indication that you are not on the right path. D. On Tue, Jul 25, 2017 at 6:25 AM, Vitaliy Biryukov <

Re: Hello

My JIRA ID: dmekhanikov Thank you! вт, 25 июл. 2017 г. в 15:09, Dmitry Pavlov : > Hi Denis, > > Welcome to the Ignite community! > > If you need contributor access to Apache JIRA, could you please sign up and > share your JIRA ID. > > Looking forward to your

Re: Changing public IgniteCompute API to improve changes in 5037 ticket

Alexei, > How would task know the partition it is running over ? Not sure it necessary. You'll create pair partition-job at task's map phase. > How can I assign task for each cache partition ? Just implement map method generates map with size equals to partition count. > How can I enforce

[GitHub] ignite pull request #2340: IGNITE-5802: Fix all wrong TODO comments in ML co...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2340 --- 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: Changing public IgniteCompute API to improve changes in 5037 ticket

Please read job instead task 2017-07-25 15:20 GMT+03:00 Alexei Scherbakov : > Main point of the issue is to provide clean API for working with > computations requiring data collocation > > affinityCall/Run provide the ability to run closure near data, but >

Re: Changing public IgniteCompute API to improve changes in 5037 ticket

Main point of the issue is to provide clean API for working with computations requiring data collocation affinityCall/Run provide the ability to run closure near data, but map/reduce API is a way reacher: continuous mapping, task session, etc. As for proposed API, I do not understand fully how

[GitHub] ignite pull request #2336: IGNITE-5770 Refactor PlatformProcessor to Platfor...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2336 --- 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: Hello

Hi Denis, Welcome to the Ignite community! If you need contributor access to Apache JIRA, could you please sign up and share your JIRA ID. Looking forward to your contributions! Sincerely, Dmitry Pavlov вт, 25 июл. 2017 г. в 14:21, Denis Mekhanikov : > Hi everyone! > >

[jira] [Created] (IGNITE-5829) Writing entry contents only single time

Pavel Kovalenko created IGNITE-5829: --- Summary: Writing entry contents only single time Key: IGNITE-5829 URL: https://issues.apache.org/jira/browse/IGNITE-5829 Project: Ignite Issue Type:

[GitHub] ignite pull request #2341: IGNITE-5648: SQL: Added support for NOT NULL cons...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/2341 IGNITE-5648: SQL: Added support for NOT NULL constraint You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Disabling assertions in tests.

Hi, Igniters! I'm working on this issue: IGNITE-5468 And to completely cover this issue with tests, I need to disable assertions. I see three solutions: 1. Make a separate test suite with disabled assertions (If I correctly understood

Hello

Hi everyone! My name is Denis, I'm from Saint Petersburg. I'd like to contribute to Apache Ignite project. I hope, you'll find my work useful. -- Best regards, Denis Mekhanikov

[GitHub] ignite pull request #2340: IGNITE-5802: Fix all wrong TODO comments in ML co...

GitHub user ybabak opened a pull request: https://github.com/apache/ignite/pull/2340 IGNITE-5802: Fix all wrong TODO comments in ML component - Added related tickets to all TODOs. - Fixed some inspection problems. You can merge this pull request into a Git repository by

[jira] [Created] (IGNITE-5828) Decompositions refactoring

Yury Babak created IGNITE-5828: -- Summary: Decompositions refactoring Key: IGNITE-5828 URL: https://issues.apache.org/jira/browse/IGNITE-5828 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5827) Benchmarks refactoring

Yury Babak created IGNITE-5827: -- Summary: Benchmarks refactoring Key: IGNITE-5827 URL: https://issues.apache.org/jira/browse/IGNITE-5827 Project: Ignite Issue Type: Bug Components: ml

[jira] [Created] (IGNITE-5826) OLS refactoring

Yury Babak created IGNITE-5826: -- Summary: OLS refactoring Key: IGNITE-5826 URL: https://issues.apache.org/jira/browse/IGNITE-5826 Project: Ignite Issue Type: Bug Components: ml

[jira] [Created] (IGNITE-5825) K-Means refactoring

Yury Babak created IGNITE-5825: -- Summary: K-Means refactoring Key: IGNITE-5825 URL: https://issues.apache.org/jira/browse/IGNITE-5825 Project: Ignite Issue Type: Bug Components: ml

[jira] [Created] (IGNITE-5824) Adjust precision in math unit tests.

Yury Babak created IGNITE-5824: -- Summary: Adjust precision in math unit tests. Key: IGNITE-5824 URL: https://issues.apache.org/jira/browse/IGNITE-5824 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #1867: incorrect construction of swap files directory pa...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1867 --- 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: [VOTE] Apache Ignite 2.1.0 RC4

+1 (binding) --Yakov 2017-07-24 16:32 GMT+03:00 Anton Vinogradov : > Igniters, > > This vote based on same files as RC3. > Only one change is that I signed zips with my signature. > KEYS files (https://dist.apache.org/repos/dist/release/ignite/KEYS) was > updated as well. > >

Re: [VOTE] Apache Ignite 2.1.0 RC4

+1 (binding) On Mon, Jul 24, 2017 at 8:32 PM, Anton Vinogradov wrote: > Igniters, > > This vote based on same files as RC3. > Only one change is that I signed zips with my signature. > KEYS files (https://dist.apache.org/repos/dist/release/ignite/KEYS) was > updated as well. >

Re: [VOTE] Apache Ignite 2.1.0 RC4

+1 (binding) On Tue, Jul 25, 2017 at 10:56 AM, Kozlov Maxim wrote: > +1 > > 25 июля 2017 г., в 10:53, Николай Ижиков > написал(а): > > > > +1 > > > > 2017-07-25 10:50 GMT+03:00 Vyacheslav Daradur : > > > >> +1 > >> > >>

Re: Changing public IgniteCompute API to improve changes in 5037 ticket

Val, Sure, we can, but we'd like to use map/reduce without fearing that topology can change. On Mon, Jul 24, 2017 at 11:17 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Anton, > > You can call affinityCallAsync multiple times and then reduce locally. > > -Val > > On Mon, Jul

Re: Timeouts in atomic cache

Guys, I have edited https://issues.apache.org/jira/browse/IGNITE-5811 and extended it a bit. Comments are welcome! --Yakov

Re: Timeouts in atomic cache

Here is the newbie ticket for removing the exception - https://issues.apache.org/jira/browse/IGNITE-5823. --Yakov

[jira] [Created] (IGNITE-5823) Need to remove CacheAtomicUpdateTimeoutException

Yakov Zhdanov created IGNITE-5823: - Summary: Need to remove CacheAtomicUpdateTimeoutException Key: IGNITE-5823 URL: https://issues.apache.org/jira/browse/IGNITE-5823 Project: Ignite Issue

Re: Timeouts in atomic cache

Val, I think this should be something similar to deadlock detection, but different condition. --Yakov

[jira] [Created] (IGNITE-5822) Abstract away Java->.NET calls

Pavel Tupitsyn created IGNITE-5822: -- Summary: Abstract away Java->.NET calls Key: IGNITE-5822 URL: https://issues.apache.org/jira/browse/IGNITE-5822 Project: Ignite Issue Type: Sub-task

Re: Ignite internal events tracing

Val, it is used by Ignite internals to report the hangs and output diagnostic information. --Yakov

Re: Resurrect FairAffinityFunction

Valentin, As far as I know in 2.0 some changes were made in rendezvous function so now it can provide better result. Do you have some numbers for 2.0 so that we can compare rendezvous and fair affinity functions? Thanks On Tue, Jul 25, 2017 at 5:13 AM, wrote: > Agree

[jira] [Created] (IGNITE-5821) Implement fuzzy checkpoints

Alexey Goncharuk created IGNITE-5821: Summary: Implement fuzzy checkpoints Key: IGNITE-5821 URL: https://issues.apache.org/jira/browse/IGNITE-5821 Project: Ignite Issue Type: New Feature

Re: [VOTE] Apache Ignite 2.1.0 RC4

+1 > 25 июля 2017 г., в 10:53, Николай Ижиков написал(а): > > +1 > > 2017-07-25 10:50 GMT+03:00 Vyacheslav Daradur : > >> +1 >> >> 2017-07-25 2:02 GMT+03:00 Valentin Kulichenko < >> valentin.kuliche...@gmail.com >>> : >> >>> +1 (binding) >>> >>>

Re: [VOTE] Apache Ignite 2.1.0 RC4

+1 2017-07-25 10:50 GMT+03:00 Vyacheslav Daradur : > +1 > > 2017-07-25 2:02 GMT+03:00 Valentin Kulichenko < > valentin.kuliche...@gmail.com > >: > > > +1 (binding) > > > > On Mon, Jul 24, 2017 at 6:39 AM, Dmitriy Setrakyan < > dsetrak...@apache.org> > > wrote: > > > > >

[jira] [Created] (IGNITE-5820) Implement ability to set auto adjust height of modal

Dmitriy Shabalin created IGNITE-5820: Summary: Implement ability to set auto adjust height of modal Key: IGNITE-5820 URL: https://issues.apache.org/jira/browse/IGNITE-5820 Project: Ignite

Re: [VOTE] Apache Ignite 2.1.0 RC4

+1 2017-07-25 2:02 GMT+03:00 Valentin Kulichenko : > +1 (binding) > > On Mon, Jul 24, 2017 at 6:39 AM, Dmitriy Setrakyan > wrote: > > > Anton, > > > > You should treat this vote as a brand new vote. According to Apache > rules, > > you need