Re: Move documentation from readme.io to GitHub pages

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 [1] https://is.gd/ZRPOrH Cos -- Take care, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions

Webinar: Apache Ignite as a backbone for microservices-based architectures

Dear community, Welcome you to join the next Apache Ignite related webinar where you can learn more about Service Grid component and how to apply it for microservices-based solutions. Description and registration: http://bit.ly/2nEmyv1  Tweet:

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

Bluntly speaking I have no idea where to look and what to expect. This is output of the test execution of my machine: SQL res: [[1], [d]] 2 Op consume: 303 Value: org.ignite.test.EDU@22db8f4 SQL res: [] 0 Op consume: 9 Value: org.ignite.test.EDU@29caf222 SQL res: [] 0 Op consume: 15 Value:

Re: Sorting fields of Binarilyzable objects on write

Vladimir, Would this be valid? *void writeBinary(BinaryWriter w) {* *if (c)* *w.writeInt("A", a)* *else* *w.writeInt("B", b)* *w.writeBoolean("C", c);* *}* D. On Wed, Apr 12, 2017 at 1:07 AM, Vladimir Ozerov wrote: > Consider the following

Re: CachePojoStore data loading with binary marshaller

On Wed, Apr 12, 2017 at 12:24 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Dmitry, > > I can't advise a lot on implementation details, but generally I don't think > that CacheJdbcPojoStore should ever work with POJO classes in case binary > marshaller is enabled. It should

Re: SQL on PARTITIONED vs REPLICATED cache

Got it, Denis. I think you are right. On Wed, Apr 12, 2017 at 2:20 PM, Denis Magda wrote: > Dmitriy, > > No, I think that Sergi supposed a type of cache which reference is used > for a query execution. In my example > > >> 2. Error-prone scenario -

Re: SQL on PARTITIONED vs REPLICATED cache

Dmitriy, No, I think that Sergi supposed a type of cache which reference is used for a query execution. In my example >> 2. Error-prone scenario - *replicatedCache*.query(“SELECT * FROM >> partitionedCache … JOIN replicatedCache …”); *replicatedCache* reference is used for the query execution

Re: Question about cache and transaction on different nodes

There is no bug. Dmitriy, you should introduce a variable: *cache0 = grid(0).cache(null);* Then you should use cache0 variable to do a cache put. You cannot use transaction API from grid0 and then cache API from grid1. In a normal environment, the cache0 and cache1 variables would not even be

Re: CREATE TABLE SQL command syntax

Got it. Can we also add CONFIGURATION keyword? On Wed, Apr 12, 2017 at 11:34 AM, Sergi Vladykin wrote: > Dmitriy, > > H2 does not support any "user-specific" syntax and it should not. Instead > it has a concept of Mode, which is basically a setting which allows H2 to >

Re: SQL on PARTITIONED vs REPLICATED cache

Denis, I think that you meant selecting from replicated cache first as an invalid scenario, but provided the wrong example. Here is the correct example for the invalid query: SELECT * FROM replicatedCache … JOIN partitionedCache …” I do agree, we should make the change, as long as we keep the

Re: Adding ML to Ignite, IGNITE-4572

As far as I know Nikita wants to provide this documentation. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Adding-ML-to-Ignite-IGNITE-4572-tp13936p16542.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: SQL on PARTITIONED vs REPLICATED cache

Sergi, As far as I understand you’re considering an example below: IgniteCache partitioneCache = ...; IgniteCache replicatedCache = …; 1. Valid scenario - *partitionedCache*.query(“SELECT * FROM partitionedCache … JOIN replicatedCache …”); 2. Error-prone scenario -

[jira] [Created] (IGNITE-4954) Timeout in ignite-cassandra SessionPool is not configurable

Valentin Kulichenko created IGNITE-4954: --- Summary: Timeout in ignite-cassandra SessionPool is not configurable Key: IGNITE-4954 URL: https://issues.apache.org/jira/browse/IGNITE-4954 Project:

Re: IGNITE-2766 Spring Cache Manager ReConnect Issue

Rishi, I don't think listening to event and OOME can be related to each other. Please investigate what is consuming memory. -Val On Wed, Apr 12, 2017 at 6:20 PM, Rishi Yagnik wrote: > Hi Val, > > Just want to share my experience here - > > with the code changes I

Re: Adding ML to Ignite, IGNITE-4572

Guys, a bit more details about the current state of ML lib and how we plan to release it. Currently IgniteML is separate module and use java8. We depends only on ignite-core module. So we think that we could release lib as sources. It should be much easier than provide our lib binary. -- View

Re: Question about cache and transaction on different nodes

Looks like a bug to me. Sergi 2017-04-12 21:03 GMT+03:00 Дмитрий Рябов : > Why not? I do something with cache inside transaction. The only reason to > not rollback is another node? > > 2017-04-12 19:52 GMT+03:00 Andrey Mashenkov : > > > Hi

Re: Question about cache and transaction on different nodes

Why not? I do something with cache inside transaction. The only reason to not rollback is another node? 2017-04-12 19:52 GMT+03:00 Andrey Mashenkov : > Hi Dmitry, > > Looks like you start transaction on node "grid(0)", but update value on > another node "grid(1)". >

Re: CREATE TABLE SQL command syntax

Hm... I think the truth is somewhere in the middle here. The syntax proposed by Sergi makes sense to me. However, I am still struggling why would H2 accept our patch, if it has AFFINITY KEY keyword in it, which has nothing to do with H2. It does sound like certain portions of SQL do need to be

Re: Question about cache and transaction on different nodes

Hi Dmitry, Looks like you start transaction on node "grid(0)", but update value on another node "grid(1)". So, technically, it is not nested transactions, right? On Wed, Apr 12, 2017 at 7:32 PM, Дмитрий Рябов wrote: > Hello, igniters. I start the node and create a

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

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1782 IGNITE-3581: CPP: Moved enums to separate structs You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3581

Question about cache and transaction on different nodes

Hello, igniters. I start the node and create a transactional cache on it, on the other node I start the transaction and "put" in previously created cache and rollback transaction. So what should I get? Value stored before transaction or inside rolled transaction? public void testRollback() throws

Re: ignite-3682 - GridFunc: move all inner anonymous classes to separate top-level classes.

Andrey, I see you've merged it before I fixed merge conflict and you fixed it yourself, thank you) There is one more unused method: public static Map viewReadOnly You can see it in my fixed version: https://github.com/apache/ignite/pull/1652/files

Re: IGNITE-2766 Spring Cache Manager ReConnect Issue

Hi Val, Just want to share my experience here - with the code changes I suggested we run into issue,out of memory on ignite with ignite thread whenever ignite cluster looses the client connection ( we had a cluster with multicast communication) . However, we changed our cluster with ip based

[GitHub] ignite pull request #1702: Ignite 4587

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/1702 --- 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 #1660: Ignite 4587 tmp

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/1660 --- 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 #1771: Ignite 3682 review

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/1771 --- 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: ignite-3682 - GridFunc: move all inner anonymous classes to separate top-level classes.

Vyacheslav, thank you for contribution! Your changes are merged into master branch. On Mon, Mar 20, 2017 at 1:11 PM, Vyacheslav Daradur wrote: > I've received answers in the issue. > > Ready for review. > > 2017-03-16 10:14 GMT+03:00 Vyacheslav Daradur

Re: CREATE TABLE SQL command syntax

If it is that little, then all this copy/paste shit-coding makes no sense. We have to add a respective mode to H2, add respective tests to H2, so that other contributors of H2 will not occasionally break our stuff. Thats it. I will be the first H2 committer who will reject you patch, don't waste

Re: Session expiration in Cassandra store

Hi Val, 1) The genral idea is to have a session pool, cause closing and reopening Cassandra session each time is rather expensive operation. 2) I can easily add session expiration timeout as a parameter for Cassandra store. Will create a ticket for this. 3) It could be easily implemented ether,

Re: question: How data are stored in IgniteCache?

In what cases BinaryObjecImpl is used? 2017-04-12 18:08 GMT+03:00 Denis Magda : > Hi, > > A cache entry is always stored in a binary format (byte array) in a cache. > Even when you transfer an entry from one node to another, as a result of > cache.put(…), operation the entry

incorrect work of IgniteLogger

Igniters! Suppose we have log4j-test.xml as following: ... ... Why damn IgniteLogger doesn't write info logs from TxOptimisticDeadlockDetectionTest class ?!? -- *Best Regards,*

Re: question: How data are stored in IgniteCache?

Hi, A cache entry is always stored in a binary format (byte array) in a cache. Even when you transfer an entry from one node to another, as a result of cache.put(…), operation the entry will be serialized into the binary format and transferred over the wire. — Denis > On Apr 12, 2017, at

[jira] [Created] (IGNITE-4953) Rework logic of concurrent schema changes

Alexander Paschenko created IGNITE-4953: --- Summary: Rework logic of concurrent schema changes Key: IGNITE-4953 URL: https://issues.apache.org/jira/browse/IGNITE-4953 Project: Ignite

[GitHub] ignite pull request #1781: Ignite 4950

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

Re: SQL on PARTITIONED vs REPLICATED cache

Yes, it's reasonable. On Wed, Apr 12, 2017 at 3:23 PM, Sergi Vladykin wrote: > Good point, but I'm not sure. The difference is that on client node you > should not be able to enable isLocal, while isReplicatedOnly is perfectly > valid. What do you think? > > Sergi > >

Re: Ignite-4795 - ready for review (Inherit TransactionException and update Javadoc)

Dmitry, thanks a lot for your contribution. Changes are merged into master branch. On Mon, Apr 10, 2017 at 7:07 PM, Andrey Gura wrote: > Thanks, Dmitry! I've reviewed your changes again and will merge it > after TC results. > > On Mon, Apr 10, 2017 at 3:08 PM, Дмитрий Рябов

[GitHub] ignite pull request #1770: ignite-4795 All transactional methods of IgniteCa...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1770 --- 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: IgniteSemaphore and failoverSafe flag

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 < dkarachent...@gridgain.com> wrote: > Hi Vladislav, > > Thanks for your contribution! But it seems doesn't fix related tickets, in >

Re: CREATE TABLE SQL command syntax

Sergi, First, it would be as little as overriding the part responsible for CREATE TABLE - there's no need to touch anything else as luckily H2 parser is internally structured well enough. Second, although it is not all-around perfect, I am most confident that this is far better than dragging

[GitHub] ignite pull request #1780: IGNITE-4173

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

[jira] [Created] (IGNITE-4952) Swapping-related Event Types must be deleted

Sergey Chugunov created IGNITE-4952: --- Summary: Swapping-related Event Types must be deleted Key: IGNITE-4952 URL: https://issues.apache.org/jira/browse/IGNITE-4952 Project: Ignite Issue

[jira] [Created] (IGNITE-4951) Discontinue AffintiyKeyMapper interface

Vladimir Ozerov created IGNITE-4951: --- Summary: Discontinue AffintiyKeyMapper interface Key: IGNITE-4951 URL: https://issues.apache.org/jira/browse/IGNITE-4951 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4950) Do not allow AffinityKeyMapped annotation on methods

Vladimir Ozerov created IGNITE-4950: --- Summary: Do not allow AffinityKeyMapped annotation on methods Key: IGNITE-4950 URL: https://issues.apache.org/jira/browse/IGNITE-4950 Project: Ignite

Re: build failure in the master branch

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 wrote: > > Does anyone has the same problem? > > 2017-04-12 12:30 GMT+03:00 Vyacheslav Daradur : > >>

Re: SQL on PARTITIONED vs REPLICATED cache

Good point, but I'm not sure. The difference is that on client node you should not be able to enable isLocal, while isReplicatedOnly is perfectly valid. What do you think? Sergi 2017-04-12 15:18 GMT+03:00 Andrey Mashenkov : > Sergi, > > Got it. > > Does query

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

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1779 IGNITE-3018 Cache affinity calculation is slow with large nodes number You can merge this pull request into a Git repository by running: $ git pull

Re: SQL on PARTITIONED vs REPLICATED cache

Sergi, Got it. Does query execution way and results will be same for isReplicatedOnly flag and for isLocal flag turned on? If my understanding is correct, we will get same results and there is no need to introduce a new flag. On Wed, Apr 12, 2017 at 2:54 PM, Sergi Vladykin

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

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 to search in another projects which use Mesos. Review please pull request - https://github.com/vadopolski/ignite/pull/2. It

Re: SQL on PARTITIONED vs REPLICATED cache

Ok, let it be an exception. I'm just saying that the thing does not work now. Sergi 2017-04-12 14:50 GMT+03:00 Andrey Mashenkov : > Sergi, > > I wounder how it is possible? > > Looks like it is impossible to run query on replicated cache, but select > data from a >

Re: SQL on PARTITIONED vs REPLICATED cache

Sergi, I wounder how it is possible? Looks like it is impossible to run query on replicated cache, but select data from a partitioned table. It will result with IlleagalStateException on stable topology or IgniteCacheException on unstable topology. See ReduceQueryExecutor.stableDataNodes() and

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

So what do u think about the issue ? ср, 12 апр. 2017 г. в 10:42, ALEKSEY KUZNETSOV : > I have already attached simlified version. Shall i simplify it more ? > > вт, 11 апр. 2017 г. в 19:28, Denis Magda : > > Can you attach the simplified version?

Re: CREATE TABLE SQL command syntax

So basically in inherited class you are going co copy/paste base class methods and tweak them? I don't like this approach. Sergi 2017-04-12 14:07 GMT+03:00 Alexander Paschenko < alexander.a.pasche...@gmail.com>: > Sergi, > > As I've written in my previous post, it would be just inheriting

Re: SQL on PARTITIONED vs REPLICATED cache

Andrey, Because if you run query on replicated cache, but select data from a partitioned table, you will get only a part of the result. Igor, You are mostly right, but 1. Performance characteristics may change. 2. Ignite SQL processing pipeline may not support all the stuff in H2 SQL and fail

Re: SQL on PARTITIONED vs REPLICATED cache

Also, is it really a breaking change if the results are wrong? To me it looks more like a bugfix, i.e. you can't break something that does not work properly. Best Regards, Igor On Wed, Apr 12, 2017 at 2:04 PM, Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: > Sergi, > > How can query to

Re: CREATE TABLE SQL command syntax

Sergi, As I've written in my previous post, it would be just inheriting Parser on Ignite side and plugging its instance in SINGLE place. Just making H2's Parser internal methods protected instead of private would let us do the trick. — Alex среда, 12 апреля 2017 г. пользователь Sergi Vladykin

Re: SQL on PARTITIONED vs REPLICATED cache

Sergi, How can query to replicated cache leads to to wrong results? Is it due to we can read backup entries? On Wed, Apr 12, 2017 at 12:31 PM, Sergi Vladykin wrote: > Guys, > > I want to introduce another breaking change for 2.0. > > Currently SQL is being processed

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

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1778 client reconnect fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3477-master-client-reconn-fix

Re: build failure in the master branch

Does anyone has the same problem? 2017-04-12 12:30 GMT+03:00 Vyacheslav Daradur : > Last commit [1] 12.04.2017 6:19:06 > > mvn -X clean package -DskipTests > > result: > *** > [DEBUG] parsing done in 2ms. > JavaDoc error: 'Other Packages' section should not be present, all >

Re: CREATE TABLE SQL command syntax

Sergey, We've already discussed this and decided to have a cache per table, because otherwise user will be forced to have unique keys across multiple independent tables, which is bad. Thus the idea with TABLESPACE does not really work for us. Sergi 2017-04-12 13:15 GMT+03:00 Sergi Vladykin

Re: CREATE TABLE SQL command syntax

I don't see how you make H2 Parser extendable, you will have to add plugin call to every *potentially* extendable place in it. In general this does not work. As H2 guy I would also reject patch like this. Sergi 2017-04-12 13:10 GMT+03:00 Alexander Paschenko < alexander.a.pasche...@gmail.com>: >

Re: CREATE TABLE SQL command syntax

Sergi, Please have a closer look at what I've written in my first post. I don't see why we have to cling to H2 and its parsing modes all the time — after all, we're just talking string processing now, aren't we? (Yes, complex and non trivial, but still.) What's wrong with idea of patching H2 to

Re: CREATE TABLE SQL command syntax

Hi I think we should introduce less new syntax for SQL for existing general statements especially inside brackets. It will simplify the migration from a RDBMS to Ignite. Personally I like idea to have CREATE CACHE syntax which similar CREATE PARTITION for MS [1] or CREATE TABLESPACE for MySQL

[GitHub] ignite pull request #1693: Ignite 4876

Github user kdudkov closed the pull request at: https://github.com/apache/ignite/pull/1693 --- 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 #1464: Ignite-4571 futId

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

Session expiration in Cassandra store

Hi Igor, I recently faced an issue with Cassandra store closing idle connections after some time. While investigating I found that this is caused by SessionPool and its SessionMonitor thread which closes sessions that were not acquired from the pool within 5 minutes. I have several questions

SQL on PARTITIONED vs REPLICATED cache

Guys, I want to introduce another breaking change for 2.0. Currently SQL is being processed differently when we call method `query` on partitioned cache and on replicated: on replicated cache we do not do any extra processing and execute the query as is on current node. This behavior

build failure in the master branch

Last commit [1] 12.04.2017 6:19:06 mvn -X clean package -DskipTests result: *** [DEBUG] parsing done in 2ms. JavaDoc error: 'Other Packages' section should not be present, all packages shou ld have corresponding documentation groups: C:\Users\SBT-Daradur-V\Projects\igni

Re: CachePojoStore data loading with binary marshaller

Yes, that's my thinking as well. -Val On Wed, Apr 12, 2017 at 10:59 AM, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com> wrote: > Hi Valentin, > > Other word, are you agree with me? My point that we always must use binary > representation if binary marshaller enable. > > On Wed, Apr 12, 2017

Re: CachePojoStore data loading with binary marshaller

Hi Valentin, Other word, are you agree with me? My point that we always must use binary representation if binary marshaller enable. On Wed, Apr 12, 2017 at 10:24 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Dmitry, > > I can't advise a lot on implementation details, but

Re: Sorting fields of Binarilyzable objects on write

Vladimir, I think we have to disallow conditional writes here, because DML should write all the fields, no? Sergi 2017-04-12 11:07 GMT+03:00 Vladimir Ozerov : > Consider the following code: > > void writeBinary(BinaryWriter w) { > w.writeBoolean("C", c); > > if

Re: CREATE TABLE SQL command syntax

It definitely makes sense to add a separate mode for Ignite in H2. Though it is wrong to think that it will allow us to add any crazy syntax we want (and it is actually a wrong idea imo), only the minor variations of the existing syntax. But this must be enough. I believe we should end up with

question: How data are stored in IgniteCache?

Hello Igniters! I have one conceptual question: When we put an object in IgniteCache, how it is stored? As I understand, after marshalling we have an array of bytes, 1) in a local node it is wrapped in BinaryObjectImpl and stored in memory 2) it is sent to remote node as byte array where it

Re: Sorting fields of Binarilyzable objects on write

Consider the following code: void writeBinary(BinaryWriter w) { w.writeBoolean("C", c); if (c) w.writeInt("A", a) else w.writeInt("B", b) } How are we going to force user to follow the contract in this case? On Wed, Apr 12, 2017 at 9:16 AM, Dmitriy Setrakyan

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

I have already attached simlified version. Shall i simplify it more ? вт, 11 апр. 2017 г. в 19:28, Denis Magda : > Can you attach the simplified version? Just want to avoid any side effects. > > — > Denis > > > On Apr 11, 2017, at 9:14 AM, ALEKSEY KUZNETSOV

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

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

Re: Sorting fields of Binarilyzable objects on write

I think it is OK for users to do their own sorting, but we should definitely validate the correct order and throw an exception if it is not. D. On Tue, Apr 11, 2017 at 11:02 PM, Pavel Tupitsyn wrote: > QueryEntity order is not only harder for the users, it will be

Re: Sorting fields of Binarilyzable objects on write

QueryEntity order is not only harder for the users, it will be nightmare to implement. What if there is no QueryEntity defined? What if the same class is used in multiple QueryEntity? I don't think serialization code has to be tied to QueryEntity in any way, this violates separation of concerns.