Re: [jira] [Updated] (IGNITE-4052) Add ability to set up users for MESOS

Hello guys! Nikolai, I improved method getRole and getUser, Review please again: https://github.com/apache/ignite/pull/1783 but what do mean about override ? Something like this: public class IgniteFrameworkUnderTest extends IgniteFramework{ ... @Override public String getUser(){ ... }

Re: Apache Ignite 2.0 Documentation

Denis, thanks for tracking the documentation changes! This is the part that usually gets missed by the community. On Thu, Apr 13, 2017 at 12:46 PM, Denis Magda wrote: > Folks, > > I’ve prepared a list of changes that have to be documented before the > public release of 2.0: >

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

I could reproduce the issue and this should be what Denis K. meant by saying “expiration policy works incorrectly”. If you remove the expiration policy from the caches' configuration then the issue disappears. In general, SQL engine processes an expiration event properly because the SQL

Re: question: How data are stored in IgniteCache?

A serialized object is always wrapped by BinaryObjectImpl when it’s stored in memory in a specific cache partition or you access it from your application in a form of BinaryObject. However, when you transfer the object over the wire or put it into a persistent store (withKeepBinary property

Re: IGNITE-2741 - spring session design

Hi Rishi, Good news :) Thanks for letting me know. -Val On Thu, Apr 13, 2017 at 9:29 PM, Rishi Yagnik wrote: > Hello Val, > > I debug further and found out that issue exist with SPA ( Angular APP ) and > it needs a fix on their end so don't worry about it. > > Next

Apache Ignite 2.0 Documentation

Folks, I’ve prepared a list of changes that have to be documented before the public release of 2.0: https://issues.apache.org/jira/browse/IGNITE-4960 That’s an impressive release and there are some many things to document. Actually, I’ll try to document the biggest part contacting contributors

[jira] [Created] (IGNITE-4979) Document SQL queries execution started on replicated cache

Denis Magda created IGNITE-4979: --- Summary: Document SQL queries execution started on replicated cache Key: IGNITE-4979 URL: https://issues.apache.org/jira/browse/IGNITE-4979 Project: Ignite

[jira] [Created] (IGNITE-4978) Prepare Apache Ignite 2.0 Migration Guide

Denis Magda created IGNITE-4978: --- Summary: Prepare Apache Ignite 2.0 Migration Guide Key: IGNITE-4978 URL: https://issues.apache.org/jira/browse/IGNITE-4978 Project: Ignite Issue Type:

Re: IGNITE-2741 - spring session design

Hello Val, I debug further and found out that issue exist with SPA ( Angular APP ) and it needs a fix on their end so don't worry about it. Next week, I will deploy it in a cluster and let you know if that fixes session replication issue on cluster. Thanks, Rishi On Thu, Apr 13, 2017 at 7:55

[jira] [Created] (IGNITE-4977) Remove BinaryIdentityResolvers mentioning from the documentation

Denis Magda created IGNITE-4977: --- Summary: Remove BinaryIdentityResolvers mentioning from the documentation Key: IGNITE-4977 URL: https://issues.apache.org/jira/browse/IGNITE-4977 Project: Ignite

[jira] [Created] (IGNITE-4976) Document C++ Continuous Queries Remote Filters

Denis Magda created IGNITE-4976: --- Summary: Document C++ Continuous Queries Remote Filters Key: IGNITE-4976 URL: https://issues.apache.org/jira/browse/IGNITE-4976 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4975) Update Hibernate documentation (Hibernate 5 addition, discontinue of binary resolvers)

Denis Magda created IGNITE-4975: --- Summary: Update Hibernate documentation (Hibernate 5 addition, discontinue of binary resolvers) Key: IGNITE-4975 URL: https://issues.apache.org/jira/browse/IGNITE-4975

[jira] [Created] (IGNITE-4974) Document .NET dynamically registered classes

Denis Magda created IGNITE-4974: --- Summary: Document .NET dynamically registered classes Key: IGNITE-4974 URL: https://issues.apache.org/jira/browse/IGNITE-4974 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4973) Document .NET Plugin System

Denis Magda created IGNITE-4973: --- Summary: Document .NET Plugin System Key: IGNITE-4973 URL: https://issues.apache.org/jira/browse/IGNITE-4973 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-4972) Document updated async API

Denis Magda created IGNITE-4972: --- Summary: Document updated async API Key: IGNITE-4972 URL: https://issues.apache.org/jira/browse/IGNITE-4972 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-4971) Document how heartbeats are issued across the cluster ring

Denis Magda created IGNITE-4971: --- Summary: Document how heartbeats are issued across the cluster ring Key: IGNITE-4971 URL: https://issues.apache.org/jira/browse/IGNITE-4971 Project: Ignite

[jira] [Created] (IGNITE-4970) Document all transactional methods

Denis Magda created IGNITE-4970: --- Summary: Document all transactional methods Key: IGNITE-4970 URL: https://issues.apache.org/jira/browse/IGNITE-4970 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-4969) Document all available thread pools including custom ones

Denis Magda created IGNITE-4969: --- Summary: Document all available thread pools including custom ones Key: IGNITE-4969 URL: https://issues.apache.org/jira/browse/IGNITE-4969 Project: Ignite

[jira] [Created] (IGNITE-4967) Document Index related commands of DDL

Denis Magda created IGNITE-4967: --- Summary: Document Index related commands of DDL Key: IGNITE-4967 URL: https://issues.apache.org/jira/browse/IGNITE-4967 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-4966) Document SQL index hints and merge sort capabilities

Denis Magda created IGNITE-4966: --- Summary: Document SQL index hints and merge sort capabilities Key: IGNITE-4966 URL: https://issues.apache.org/jira/browse/IGNITE-4966 Project: Ignite Issue

[jira] [Created] (IGNITE-4965) Document enum fileds handling and changes with 'select * ...' in SQL

Denis Magda created IGNITE-4965: --- Summary: Document enum fileds handling and changes with 'select * ...' in SQL Key: IGNITE-4965 URL: https://issues.apache.org/jira/browse/IGNITE-4965 Project: Ignite

[GitHub] ignite pull request #1791: Ignite 4927

GitHub user abeliak opened a pull request: https://github.com/apache/ignite/pull/1791 Ignite 4927 Don't merge You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4927 Alternatively you can review and

[GitHub] ignite pull request #1784: Ignite 4927

Github user abeliak closed the pull request at: https://github.com/apache/ignite/pull/1784 --- 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: Adding ML to Ignite, IGNITE-4572

Hi Oleg, That’s great, thanks. I’ve created a JIRA ticket for this task and assigned on Nikita for now. Please create an account for yourself and reassign the ticket if needed: https://issues.apache.org/jira/browse/IGNITE-4964 Plus, there is an invisible page on readme.io

[jira] [Created] (IGNITE-4964) Document Machine Learning Grid (Distributed Algebra Implementation)

Denis Magda created IGNITE-4964: --- Summary: Document Machine Learning Grid (Distributed Algebra Implementation) Key: IGNITE-4964 URL: https://issues.apache.org/jira/browse/IGNITE-4964 Project: Ignite

[jira] [Created] (IGNITE-4963) Document cache store metrics based on page memory

Denis Magda created IGNITE-4963: --- Summary: Document cache store metrics based on page memory Key: IGNITE-4963 URL: https://issues.apache.org/jira/browse/IGNITE-4963 Project: Ignite Issue

[jira] [Created] (IGNITE-4962) Document New Eviction and Expiration Policies

Denis Magda created IGNITE-4962: --- Summary: Document New Eviction and Expiration Policies Key: IGNITE-4962 URL: https://issues.apache.org/jira/browse/IGNITE-4962 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4961) Document Page Memory API, Architecture and Behavior

Denis Magda created IGNITE-4961: --- Summary: Document Page Memory API, Architecture and Behavior Key: IGNITE-4961 URL: https://issues.apache.org/jira/browse/IGNITE-4961 Project: Ignite Issue

[jira] [Created] (IGNITE-4960) Apache Ignite 2.0 Documentation

Denis Magda created IGNITE-4960: --- Summary: Apache Ignite 2.0 Documentation Key: IGNITE-4960 URL: https://issues.apache.org/jira/browse/IGNITE-4960 Project: Ignite Issue Type: Task

Re: Adding ML to Ignite, IGNITE-4572

Yury, Denis - me and Nikita are going to take care of readme.io docs. I plan to start on this tomorrow, will keep you posted on the progress. Current plan is to briefly introduce new package and examples and explain how to run examples and possibly unit tests. With regards to build details,

[GitHub] ignite pull request #1790: IGNITE-3488

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

[GitHub] ignite pull request #1789: IGNITE-3524 IGFS: Do not allow nulls for FileSyst...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1789 IGNITE-3524 IGFS: Do not allow nulls for FileSystemConfiguration.name You can merge this pull request into a Git repository by running: $ git pull

Re: Move documentation from readme.io to GitHub pages

On Wed, Apr 12, 2017 at 8:52 PM, Konstantin Boudnik wrote: > I hate to be that guy, but mentors warned this very project no to do > this in the first place. At least once [1] on the dev@, and a few > times off-line > Cos, no doubt this had come up before (after all, we did have

[jira] [Created] (IGNITE-4959) Possible slight memory leak in free list

Ivan Rakov created IGNITE-4959: -- Summary: Possible slight memory leak in free list Key: IGNITE-4959 URL: https://issues.apache.org/jira/browse/IGNITE-4959 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4958) Make data pages recyclable into index/meta/etc pages and vice versa

Ivan Rakov created IGNITE-4958: -- Summary: Make data pages recyclable into index/meta/etc pages and vice versa Key: IGNITE-4958 URL: https://issues.apache.org/jira/browse/IGNITE-4958 Project: Ignite

[GitHub] ignite pull request #1788: IGNITE-4952 swap/unswap functionality was removed

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1788 IGNITE-4952 swap/unswap functionality was removed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: [jira] [Commented] (IGNITE-4052) Add ability to set up users for MESOS

Vadim, I've left comment in the ticket. On Wed, Apr 12, 2017 at 3:00 PM, Вадим Опольский wrote: > Hello guys! > > Nikolay, I looked at cassandra mesos integration, but cant find how to > test ability to configure mesos and user via system env properties. I will > continue

Re: Synchronize method across Ignite cluster

>> Lock lock = cache.lock(key); - works only >> with CacheAtomicityMode.TRANSACTIONAL Correct >> Does cache-locks work across all nodes of Ignite-cluster? Yes >> what an approach will be the best for use >> within IGNITE-4211. EntryProcessor is the best case, but, seems, it can't be used due to

Re: IgniteSemaphore and failoverSafe flag

Thanks a lot! 12.04.2017 16:35, Vladisav Jelisavcic пишет: Hi Dmitry, sure, I made a fix, take a look at the PR and the comments in the ticket. Best regards, Vladisav On Tue, Apr 11, 2017 at 3:00 PM, Dmitry Karachentsev > wrote:

Re: Synchronize method across Ignite cluster

Anton, you all know for what I need it)) As I understand: Lock lock = cache.lock(key); - works only with CacheAtomicityMode.TRANSACTIONAL Does cache-locks work across all nodes of Ignite-cluster? Can you give me some advice: what an approach will be the best for use within IGNITE-4211. (you

[GitHub] ignite pull request #1779: IGNITE-3018 Cache affinity calculation is slow wi...

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

Re: Synchronize method across Ignite cluster

Vyacheslav, Explicit cache locks, DataStructures (eg. reentrant locks), transactions, etc. We have all of them and even more :) On Thu, Apr 13, 2017 at 3:54 PM, Vyacheslav Daradur wrote: > Hi Igniters! > > I need to synchronize a method across a Ignite cluster, which work

[jira] [Created] (IGNITE-4957) First join query execution in client mode takes too long when there are many caches on remote nodes

Alexandr Fedotov created IGNITE-4957: Summary: First join query execution in client mode takes too long when there are many caches on remote nodes Key: IGNITE-4957 URL:

Re: IGNITE-2741 - spring session design

Val, Yes I would provide you the exact steps today and I will also test it in cluster environment. The local environment is working as expected with the fix. Take Care, Rishi > On Apr 13, 2017, at 2:18 AM, Valentin Kulichenko > wrote: > > Rishi, > > Can you

Synchronize method across Ignite cluster

Hi Igniters! I need to synchronize a method across a Ignite cluster, which work with IgniteCache. Does Ignite provide any tools for? For example: *** Lock lock = cache.lock(key); lock.lock(); try { // todo somethink } finally { lock.unlock(); } *** -- Best Regards, Vyacheslav

Re: IGNITE - 4760 ready for review

Semyon, thanks for comments. - I will change access type for created region. - USE_STRUCTURED_CACHE property needs to store data in cache in a more readable format. Without it I cant cast data from cache to String and HashMap. - I will add the same test for READ_WRITE access strategy. - I will

[GitHub] ignite pull request #1205: IGNITE-4155 minor fixes to examples

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1205 --- 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

[GitHub] ignite pull request #1744: Ignite 3477 master client offheap fix

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1744 --- 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

[GitHub] ignite pull request #1754: Ignite 3477 client hash index fix

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1754 --- 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

[GitHub] ignite pull request #1769: Ignite 3477 master CPP Win32 OOM fix

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1769 --- 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

[GitHub] ignite pull request #1778: client reconnect fix

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1778 --- 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

Re: IGNITE - 4760 ready for review

Hi Vadim, I added comments in JIRA. I'll apply the same fix for hibernate5 when fix is finalized. Thanks! On Thu, Apr 13, 2017 at 12:10 PM, Вадим Опольский wrote: > Hi, guys! > > Semyon, have you had a time to review IGNITE-4760 >

[jira] [Created] (IGNITE-4956) Stabilize the test IgniteCacheLockPartitionOnAffinityRunAtomicCacheOpTest.testNotReservedTxCacheOp

Taras Ledkov created IGNITE-4956: Summary: Stabilize the test IgniteCacheLockPartitionOnAffinityRunAtomicCacheOpTest.testNotReservedTxCacheOp Key: IGNITE-4956 URL:

[GitHub] ignite pull request #1782: IGNITE-3581: CPP: Moved enums to separate structs

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1782 --- 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 #1787: IGNITE-2398 .NET: Change default mapper behavior

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1787 IGNITE-2398 .NET: Change default mapper behavior You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2398

[GitHub] ignite pull request #1777: IGNITE-2398 .NET: Change default mapper behavior

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/1777 --- 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: Sorting fields of Binarilyzable objects on write

Vova, can you give an example of when writing out of order would be the only option? On Thu, Apr 13, 2017 at 4:20 AM, Vladimir Ozerov wrote: > Folks, > > If you restrict writes in certain order and conditions, Binarylizable > interfaces turns into an unusable bullshit :-)

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

any feedback? чт, 13 апр. 2017 г. в 11:51, ALEKSEY KUZNETSOV : > You should run ExpiryPolicyTest. The output should contain strings like > contains? new AffinityKey("1", "1"): and contains?2 new AffinityKey("1", " > 1"): and empty cursor? = > If you look at them you

Re: Sorting fields of Binarilyzable objects on write

Folks, If you restrict writes in certain order and conditions, Binarylizable interfaces turns into an unusable bullshit :-) Remember that not all binary objects participate in DML, and even if so, not all binary objects are cache keys. I think we should simply print a warning to log, informing

Re: Sorting fields of Binarilyzable objects on write

That is cool, completely forgot about it :) 2017-04-13 14:07 GMT+03:00 Pavel Tupitsyn : > Alexey, we can read fields in any order in non-raw mode. > Dmitriy's suggestion would work. > > On Thu, Apr 13, 2017 at 1:56 PM, Alexey Goncharuk < > alexey.goncha...@gmail.com> wrote:

Re: Sorting fields of Binarilyzable objects on write

Alexey, we can read fields in any order in non-raw mode. Dmitriy's suggestion would work. On Thu, Apr 13, 2017 at 1:56 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Dmitriy, > > How would then reader determine which field to read (a and b could the of > different size)? c in this

Re: Sorting fields of Binarilyzable objects on write

Dmitriy, How would then reader determine which field to read (a and b could the of different size)? c in this case must be written first. 2017-04-13 0:29 GMT+03:00 Dmitriy Setrakyan : > Vladimir, > > Would this be valid? > > *void writeBinary(BinaryWriter w) {* > > *

Re: CREATE TABLE SQL command syntax

CREATE TABLE () WITH "cacheCfgUrl or templateName or anything you want" Sergi 2017-04-13 12:43 GMT+03:00 Dmitriy Setrakyan : > Sergi, > > I would avoid exposing the word "CACHE" on the SQL side. I prefer that we > work with tables. I can see a use for a

Re: CREATE TABLE SQL command syntax

Sergi, I would avoid exposing the word "CACHE" on the SQL side. I prefer that we work with tables. I can see a use for a table_configuration(...) function to create configuration templates, but how would you associate a configuration template with a table inside of "create table" statement? D.

Re: CachePojoStore data loading with binary marshaller

On Thu, Apr 13, 2017 at 12:16 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > It's not illegal in general, but it doesn't make sense for out of the box > implementation of cache store.\ > Ouch. I didn't realize that we deserialize in our own cache store. Any reason for this

[GitHub] ignite pull request #1786: IGNITE-3523 IGFS: Remove "initialize default path...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1786 IGNITE-3523 IGFS: Remove "initialize default path modes" feature You can merge this pull request into a Git repository by running: $ git pull

Re: IGNITE - 4760 ready for review

Hi, guys! Semyon, have you had a time to review IGNITE-4760 https://github.com/apache/ignite/pull/1768 ? Is this fix actual for hibernate5 module? Vadim Opolski 2017-04-11 13:40 GMT+03:00 Semyon Boikov : > Thanks Vadim, I'll try to do review today. > > Semyon > > On Mon,

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

You should run ExpiryPolicyTest. The output should contain strings like contains? new AffinityKey("1", "1"): and contains?2 new AffinityKey("1", "1" ): and empty cursor? = If you look at them you will see, that cache contains affinity key new AffinityKey("1", "1") whereas cursor is empty(on second

[GitHub] ignite pull request #1785: IGNITE-4954 - Configurable expiration timeout for...

GitHub user vkulichenko opened a pull request: https://github.com/apache/ignite/pull/1785 IGNITE-4954 - Configurable expiration timeout for Casssndra session You can merge this pull request into a Git repository by running: $ git pull https://github.com/vkulichenko/ignite

Re: build failure in the master branch

Rishi, thank you. It is building well, with commits before 12.04.17 2017-04-12 15:37 GMT+03:00 Rishi Yagnik : > I build it last night it worked for me..I am using Jdk8-121, hope that > helps .. > > Take Care, > Rishi > > > On Apr 12, 2017, at 5:37 AM, Vyacheslav Daradur

[GitHub] ignite pull request #1784: Ignite 4927

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

Re: question: How data are stored in IgniteCache?

Denis, thank you for answers. I meant another. For example: Cache queries use a BinaryObjectImpl and a withKeepBinary-mode use it, so looks like all actions on serialized object are make via a BinaryObjectImpl. Does a serialized object always is stored as BinaryObjectImpl or it will be wrapped

Re: IGNITE-2741 - spring session design

Rishi, Can you tell exact steps to reproduce? It's working for me in my environment. Do I understand correctly that apart from the token issue, it works fine with new version? -Val On Wed, Apr 12, 2017 at 10:00 PM, Rishi Yagnik wrote: > Val, > > I build it from master

Re: CachePojoStore data loading with binary marshaller

It's not illegal in general, but it doesn't make sense for out of the box implementation of cache store. -Val On Wed, Apr 12, 2017 at 11:27 PM, Dmitriy Setrakyan wrote: > On Wed, Apr 12, 2017 at 12:24 AM, Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > >

[jira] [Created] (IGNITE-4955) Correctly execute SQL queries started on replicated cache.

Sergi Vladykin created IGNITE-4955: -- Summary: Correctly execute SQL queries started on replicated cache. Key: IGNITE-4955 URL: https://issues.apache.org/jira/browse/IGNITE-4955 Project: Ignite

Re: CREATE TABLE SQL command syntax

I do not think we need it. In standard SQL we already have KEY and COLUMN, also we already have CREATE TABLE syntax. Adding AFFINITY to them is not a big deal. The thing CONFIGURATION looks like a completely new entity for SQL and I prefer to avoid sticking it into H2, also I would avoid having

Re: Session expiration in Cassandra store

Hi Val, Keeping session forever is not good cause it consumes resources on server and client side as well. On the client for example you have bunch of Netty threads. I think if you just specify session expiration timeout to some big value (1 day for example) it should be far enough. Igor On

Re: Question about cache and transaction on different nodes

Yes, sorry. The test works correctly: tx started on grid0 does not affect cache1, because they are on different nodes. Thus the operation cache1.put(1, ) is successfully committed. Still I would not recommend to rely on any of observed behaviors here, because Ignite was not designed for