Re: DML data streaming

Dima, Value type name doesn't necessarily maps to table name. For instance, what if I have two tables like this? They both have "java.lang.Long" as type name. CREATE table *t1* { pk_id BIGINT PRIMARY KEY, val BIGINT } CREATE table *t2* { pk_id BIGINT PRIMARY KEY, val BIGINT }

Re: IGNITE-2626 is cloned?

Yes, IGNITE-3191 resolves the problem mentioned in IGNITE-2626. No configuration parameter needed. We have system property to control this, but only for compatibility reasons - without it users might have lost ability to migrate from [1.x] to 1.[x+1] if they persist objects outside of Ignite. On

FullText index can't be disabled for cache with String values.

Igniters, I've found that we can't use SORTED index only for cache with String values. FULLTEXT index has always being created in IgniteH2Indexing.TableDescriptor.createIndexes(). I've create a ticket IGNITE-4715 [1]. Serji, please, take a look at this. [1]

[jira] [Created] (IGNITE-4715) SQL: FullText index can't be disabled for cache with String values.

Andrew Mashenkov created IGNITE-4715: Summary: SQL: FullText index can't be disabled for cache with String values. Key: IGNITE-4715 URL: https://issues.apache.org/jira/browse/IGNITE-4715

Re: error - Failed to wait for partition release future

Hi Cameron, It looks like nodes cant see each other. Would you please attach grid configuration and full logs? BTW, ignite version on nodes still "ver=1.8.1#20161208-sha1:a8fcb7b2" On Fri, Feb 17, 2017 at 2:15 AM, Cameron Braid wrote: > Ok, I have moved to using apache

Re: New documentation domain for tooling

BTW, you don’t need to bookmark this new documentation domain. Just go to the main one: https://apacheignite.readme.io/docs/ and in the header you’ll find tabs for all distinct docs we have - .NET, C++, Spark, Integrations and Tools. — Denis > On Feb 16, 2017, at 7:52 PM, Denis Magda

Re: IGNITE-2626 is cloned?

Taras, Vovan, Did IGNITE-3191 [1] automatically solve the problem described in [2]? If it’s so I would close [2]. BTW, did we add a new configuration parameter as a part of [1] dev activity? [1] https://issues.apache.org/jira/browse/IGNITE-3191 [2]

New documentation domain for tooling

Igniters, Let me introduce a new documentation domain for Ignite’s tooling: https://apacheignite-tools.readme.io/docs/ignite-web-console Presently, there you will find docs for Web Console, Visor CLI, Zeppelin & Tableau integrations. *Prachi*, could you review the following pages?

[jira] [Created] (IGNITE-4714) Web console: Disable refresh rate for explain query

Vasiliy Sisko created IGNITE-4714: - Summary: Web console: Disable refresh rate for explain query Key: IGNITE-4714 URL: https://issues.apache.org/jira/browse/IGNITE-4714 Project: Ignite Issue

Re: error - Failed to wait for partition release future

Ok, I have moved to using apache ignite 1.8.0 jar and the same issue is there. I don't believe that it is slow networking that is causing this as it does also happen on a single host single node cluster - its hard to reproduce but it does happen. I've included a log from the grid locking up

Re: DML data streaming

Vladimir, I am not sure I understand your point. The value type name should be the table name, no? On Thu, Feb 16, 2017 at 12:13 AM, Vladimir Ozerov wrote: > Dima, > > At this point we require the following additional data which is outside of > standard SQL: > - Key type >

Re: DML usability: routing single column to several object fields

Vladimir, When a table is created, user should specify the "primary key". We can extract this field and use it as the key into the BTree index. This way it will fit into the current design. Am I wrong? D. On Thu, Feb 16, 2017 at 4:33 AM, Vladimir Ozerov wrote: >

cache metadata progapagation

Igniters, I believe that we are not propagating cache metadata correctly, but I want to confirm it with the community first. Currently, it is possible in Ignite to split the cluster into logical groups, and deploy caches only on certain nodes using NodeFilters. For example, CacheA will reside

[GitHub] ignite pull request #1515: IGNITE-4158

Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/1515 --- 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 #1548: IGNITE-4611

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

IGNITE-4713 : refactoring of GridFinishedFuture and GridFutureAdapter

Hello. I propose to do refactoring of classes "GridFinishedFuture" and "GridFutureAdapter". There is field "resFlag" which can equals "ERR = 1" or "RES = 2". So I can replace it to one "bool haveResult" field. If there are no objections, I'm ready to proceed. If you find more such classes,

[jira] [Created] (IGNITE-4713) refactoring of GridFinishedFuture and GridFutureAdapter

Alexander Menshikov created IGNITE-4713: --- Summary: refactoring of GridFinishedFuture and GridFutureAdapter Key: IGNITE-4713 URL: https://issues.apache.org/jira/browse/IGNITE-4713 Project:

Re: error - Failed to wait for partition release future

Hi Cameron, You wrote on Apache Ignite Community dev-list. Iginte does not have versions like 1.8.x. Git repository you refer to is not belong to the Apache Ignite project. On Thu, Feb 16, 2017 at 6:58 PM, Cameron Braid wrote: > Hi, > > Thanks for looking at my issue. >

Re: error - Failed to wait for partition release future

Hi, Thanks for looking at my issue. There are tags for 1.8.1, 1.8.2 and 1.8.3 at https://github.com/gridgain/apache-ignite so I have been trying using jars built from those tags, including 1.9 I'm still getting the issues. What concerns me the most is that it is very easy to lockup the whole

Re: ignite analysis with jepsen

Evgeniy, The price is high if you want Jepsen guys to do the testing of Ignite with their suites. We, as open source community, can’t afford it. However, I didn’t know that the tests are open sourced. Is this something are ready to take over? — Denis > On Feb 15, 2017, at 10:23 PM, Evgeniy

Re: Implement IgniteZeromqStreamer to stream data from ZeroMQ

Roman, As the most experienced committer of the streaming components, could you do the review of Maxim’s changes? — Denis > On Feb 16, 2017, at 1:23 AM, Kozlov Maxim wrote: > > Hello Igniters, > > Please review and comment implementation ZeroMQ streamer. > PR:

[jira] [Created] (IGNITE-4712) Memory leaks in PageMemory

Igor Seliverstov created IGNITE-4712: Summary: Memory leaks in PageMemory Key: IGNITE-4712 URL: https://issues.apache.org/jira/browse/IGNITE-4712 Project: Ignite Issue Type: Bug

Re: Apache Ignite 1.9

Anton, However, I would like Serj or somebody else take a look at IGNITE-4106. On Thu, Feb 16, 2017 at 6:07 PM, Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: > Anton, > > IGNITE-4106 is done. > > On Thu, Feb 16, 2017 at 5:36 PM, Igor Sapego wrote: > >> Anton, >>

Re: Apache Ignite 1.9

Anton, IGNITE-4106 is done. On Thu, Feb 16, 2017 at 5:36 PM, Igor Sapego wrote: > Anton, > > IGNITE-4670 is almost ready. I believe, there is nothing to worry about. > > Best Regards, > Igor > > On Thu, Feb 16, 2017 at 5:16 PM, Alexander Paschenko < >

[GitHub] ignite pull request #1543: IGNITE-4628 Add Java callback support for platfor...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/1543 --- 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: Apache Ignite 1.9

Anton, IGNITE-4670 is almost ready. I believe, there is nothing to worry about. Best Regards, Igor On Thu, Feb 16, 2017 at 5:16 PM, Alexander Paschenko < alexander.a.pasche...@gmail.com> wrote: > Hi, > > There are some questions regarding IGNITE-4169 - probably some design > approval will be

[GitHub] ignite pull request #1547: IGNITE-4670: Added LoadCache and LocalLoadCache m...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1547 IGNITE-4670: Added LoadCache and LocalLoadCache methods You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4670

[GitHub] ignite pull request #1546: Ignite 3710 Upgrade ignite-spark module to Spark ...

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/1546 Ignite 3710 Upgrade ignite-spark module to Spark 2.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3710

IGNITE-2779 BinaryMarshaller caches must be cleaned during client reconnect.

will take the ticket https://issues.apache.org/jira/browse/IGNITE-2779 -- *Best Regards,* *Kuznetsov Aleksey*

Re: Apache Ignite 1.9

Hi, There are some questions regarding IGNITE-4169 - probably some design approval will be required from Dmitry S. However, chances are good that we'll make it in time. - Alex 2017-02-16 14:48 GMT+03:00 Anton Vinogradov : > Igniters, > > We're planning to have a code

[GitHub] ignite pull request #1545: IGNITE-2552 EvictionPolicies refactored, logic ch...

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/1545 IGNITE-2552 EvictionPolicies refactored, logic changed tests are in subclasses of EvictionAbstractTest You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-4711) Propagate platform cache plugin configuration to Java

Pavel Tupitsyn created IGNITE-4711: -- Summary: Propagate platform cache plugin configuration to Java Key: IGNITE-4711 URL: https://issues.apache.org/jira/browse/IGNITE-4711 Project: Ignite

[GitHub] ignite pull request #1544: IGNITE-4710: extended optimistic tx lock conflict...

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/1544 IGNITE-4710: extended optimistic tx lock conflict exception message You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1500: ignite-3477-idx2

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

Hi Alexey, See how org.apache.ignite.internal.processors.cache.CacheEvictableEntryImpl.meta() is used by, e.g. org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicy.touch() method that is calling when entry accessed. On Wed, Feb 15, 2017 at 6:10 PM, ALEKSEY KUZNETSOV

[GitHub] ignite pull request #1542: IGNITE-4710 extended optimistic tx lock conflict ...

Github user zstan closed the pull request at: https://github.com/apache/ignite/pull/1542 --- 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 #1543: IGNITE-4628 Add Java callback support for platfor...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1543 IGNITE-4628 Add Java callback support for platform plugins You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

DML usability: routing single column to several object fields

Igniters, Consider the following pattern which is typically used by users when working through cache API and quering data through SQL at the same time: class Person { @QuerySqlField long id; @QuerySqlField String name; } cache.put(*id*, new Person(*id*, name)); SELECT *id*,

IGNITE-2626 is cloned?

Hi! about https://issues.apache.org/jira/browse/IGNITE-2626. Im sure this ticket is cloned from https://issues.apache.org/jira/browse/IGNITE-3191, because it was implemented there. And im confused with code status : fields order is somehow deprecated. This ticket -

Re: Apache Ignite 1.9

Igniters, We're planning to have a code freeze tomorrow, Feb 17 19.00 MSK. Here's the list of issues we especially expect to be done in 1.9: IGNITE-4106 SQL: parallelize sql queries over cache local partitions Andrew Mashenkov IGNITE-4670 CPP: Implement LoadCache method Task Igor Sapego

Re: IGNITE-602

Yes, my idea was around it - we need to stop recursion somehow. On the other hand, position-based format is not very user-friendly, apparently. May be some other approaches will be more suitable, but I cannot think of anything else. On Thu, Feb 16, 2017 at 2:26 PM, Дмитрий Рябов

[GitHub] ignite pull request #1542: IGNITE-4710 extended optimistic tx lock conflict ...

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/1542 IGNITE-4710 extended optimistic tx lock conflict exception message You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1541: IGNITE-4710 extended optimistic tx lock conflict ...

Github user zstan closed the pull request at: https://github.com/apache/ignite/pull/1541 --- 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: Apache Ignite 1.9

Denis, Evgenii Zhuravlev going to fix this issue. I'll provide him help if necessarry. On Wed, Feb 15, 2017 at 8:03 PM, Denis Magda wrote: > Anton, > > The implementation is correct and was reviewed by Val long time ago. The > only issue that is left is the compilation in

Re: IGNITE-602

Hello, Vladimir. Do you mean something like "ArrayList [size=1, name=ArrayList [size=1, ArrayList {position 0}]]"? 2017-02-16 12:32 GMT+03:00 Vladimir Ozerov : > Hi Dmitriy, > > We should print all objects, because this is the whole purpose of > GridToStringBuilder class -

[GitHub] ignite pull request #1541: Ignite 4710

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

[GitHub] ignite pull request #1540: Ignite 4710

Github user zstan closed the pull request at: https://github.com/apache/ignite/pull/1540 --- 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: error - Failed to wait for partition release future

Hi Cameron, Ignite does not have 1.8.x versions. It look like you use IPv6 on some of you nodes. At first, check if either -Djava.net.preferIPv6Addresses=true or -Djava.net.preferIPv4Addresses=true java option is set for all of your nodes and communication port is set properly. On Thu, Feb 16,

[GitHub] ignite pull request #1540: Ignite 4710

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

[jira] [Created] (IGNITE-4710) Better optimistic tx lock conflict client information.

Stanilovsky Evgeny created IGNITE-4710: -- Summary: Better optimistic tx lock conflict client information. Key: IGNITE-4710 URL: https://issues.apache.org/jira/browse/IGNITE-4710 Project: Ignite

IGNITE-1624: [Test failed] Ignite SPI: TcpClientDiscoverySpiSelfTest.testJoinError failed

Hello. I try to fix test. But can't reproduce problem. I added reps in a loop and ran test local 10 minutes. There aren't problem. After that I set 1500 reps and ran on CI (my local machine can do 1900 reps in 5 minutes) and got timeout, but not the origin problem from issue. Anyone have any

Re: IGNITE-602

Hi Dmitriy, We should print all objects, because this is the whole purpose of GridToStringBuilder class - to print as much as possible in pretty format. For cyclic references, we should introduce smarter approach, ensuring that certain object is printed only once, I would use a kind of stack or

Implement IgniteZeromqStreamer to stream data from ZeroMQ

Hello Igniters, Please review and comment implementation ZeroMQ streamer. PR: https://github.com/apache/ignite/pull/1532 Jira: https://issues.apache.org/jira/browse/IGNITE-533 -- Best Regards, Max

[jira] [Created] (IGNITE-4709) Web Console: Implement support for Affinity key configuration on Model screen

Alexey Kuznetsov created IGNITE-4709: Summary: Web Console: Implement support for Affinity key configuration on Model screen Key: IGNITE-4709 URL: https://issues.apache.org/jira/browse/IGNITE-4709

[jira] [Created] (IGNITE-4708) Web Console: Show detailed information about error on Queries screen

Alexey Kuznetsov created IGNITE-4708: Summary: Web Console: Show detailed information about error on Queries screen Key: IGNITE-4708 URL: https://issues.apache.org/jira/browse/IGNITE-4708

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

thankx чт, 16 февр. 2017 г. в 11:29, Alexey Kuznetsov : > Hi! > > I did minor code-style review directly on GitHub. Please fix. > > But some one who knows GridCacheProcessor.java should do one more review. > > On Thu, Feb 16, 2017 at 2:38 PM, ALEKSEY KUZNETSOV < >

Re: IGNITE-2626 Binary marshaller: sort fields alphabetically

yeap чт, 16 февр. 2017 г. в 11:26, Vyacheslav Daradur : > Hello. > > Look at the ticket: https://issues.apache.org/jira/browse/IGNITE-4695 > - Write primitive fields before during binary object marshalling > > Maybe it relates. > > 2017-02-16 11:18 GMT+03:00 ALEKSEY

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

Hi! I did minor code-style review directly on GitHub. Please fix. But some one who knows GridCacheProcessor.java should do one more review. On Thu, Feb 16, 2017 at 2:38 PM, ALEKSEY KUZNETSOV wrote: > Plz, review my PR : https://github.com/apache/ignite/pull/1517 > >

Re: IGNITE-2626 Binary marshaller: sort fields alphabetically

Hello. Look at the ticket: https://issues.apache.org/jira/browse/IGNITE-4695 - Write primitive fields before during binary object marshalling Maybe it relates. 2017-02-16 11:18 GMT+03:00 ALEKSEY KUZNETSOV : > im going to take

IGNITE-2626 Binary marshaller: sort fields alphabetically

im going to take https://issues.apache.org/jira/browse/IGNITE-2626 -- *Best Regards,* *Kuznetsov Aleksey*

Re: DML data streaming

Dima, At this point we require the following additional data which is outside of standard SQL: - Key type - Value type - Set of key columns I do not know yet how we will define these values. At the very least we can calculate them automatically in some cases. For "keyFieldName" and