Re: Null cache names

Shall we add the notes to REST and memcached docs pages that "default" cache has to be specified in xml configs? Otherwise it is not created and "cacheName" cannot be optional (as REST API docs say) -- no default cache. https://apacheignite.readme.io/docs/rest-api -- Roman On Monday,

Re: Supported and Unsupported SQL

Ticket filed: https://issues.apache.org/jira/browse/IGNITE-5678 On Mon, Jul 3, 2017 at 5:14 PM, Denis Magda wrote: > Fully support this idea. That’ll help a lot our users and make things > clearer for us. > > — > Denis > > > On Jul 3, 2017, at 8:41 AM, Dmitriy Setrakyan

[jira] [Created] (IGNITE-5678) Need to document and test supported and unsupported SQL features

Dmitriy Setrakyan created IGNITE-5678: - Summary: Need to document and test supported and unsupported SQL features Key: IGNITE-5678 URL: https://issues.apache.org/jira/browse/IGNITE-5678 Project:

Re: Supported and Unsupported SQL

Fully support this idea. That’ll help a lot our users and make things clearer for us. — Denis > On Jul 3, 2017, at 8:41 AM, Dmitriy Setrakyan wrote: > > Igniters, > > Vladimir pointed out that PostgreSQL has a very detailed list of supported > and unsupported features:

[jira] [Created] (IGNITE-5677) Document affinity-related SQL optimizations

Denis Magda created IGNITE-5677: --- Summary: Document affinity-related SQL optimizations Key: IGNITE-5677 URL: https://issues.apache.org/jira/browse/IGNITE-5677 Project: Ignite Issue Type:

Re: Distributed scheduling

Hm... I think we should definitely make our services durable. Everything in Ignite should be durable now. As far as scheduling, makes sense as well. Let's make it durable too. D. On Mon, Jul 3, 2017 at 3:35 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Dmitry, > > Yes, this

Re: Distributed scheduling

Dmitry, Yes, this can be implemented using services in many cases, but: - It will require user to implement actual scheduling logic. It's quite a generic task, so I think it makes sense to have it directly on the API. - Most likely it will imply deploying separate service for each scheduled

Re: Zookeeper Discovery SPI & external IP address in AWS

To my knowledge it's the case, there should be any issues with that. -Val On Mon, Jul 3, 2017 at 3:55 AM, Yakov Zhdanov wrote: > My point is that communication SPI should put both address types to its > attributes to share - private and addresses processed by a resolver. >

Re: Custom string encoding

Yes, this needs to be tested and confirmed. I will work on it. Would be great to get more details about indexes. I'm not sure I understand the limitation there. -Val On Mon, Jul 3, 2017 at 7:21 AM, Dmitriy Setrakyan wrote: > Agree with Valya on the system-wide default.

Re: Ready for review IGNITE-5532 .NET: Clean up and refactor CacheLinqTest

Hi, Anton Thank you for suggestion, done. On 3 July 2017 at 20:22, Anton Vinogradov wrote: > Hi, > > Thanks for interest to Apache Ignite development. > > I'd like to propose you to make direct "review request". > This should help to speedup review process, you can

[GitHub] ignite pull request #2228: IGNITE-5153 CPP: Introduced "varint" encoding in ...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2228 IGNITE-5153 CPP: Introduced "varint" encoding in C++ You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5153_2

Re: Ready for review IGNITE-5532 .NET: Clean up and refactor CacheLinqTest

Hi, Thanks for interest to Apache Ignite development. I'd like to propose you to make direct "review request". This should help to speedup review process, you can find tips here: https://cwiki.apache.org/confluence/display/IGNITE/How+ to+Contribute#HowtoContribute-SubmittingforReview On Mon,

[GitHub] ignite pull request #2227: IGNITE-5159 DDL example.

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2227 IGNITE-5159 DDL example. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5159 Alternatively you can

Ready for review IGNITE-5532 .NET: Clean up and refactor CacheLinqTest

Hi, IGNITE-5532 is ready for review, can someone take a look please? https://github.com/apache/ignite/pull/2226 Builds: Ignite Platform .NET http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgnitePlatformNet_Ignite20Tests=pull%2F2226%2Fmerge=buildTypeStatusDiv Ignite

[GitHub] ignite pull request #2226: IGNITE-5532 .NET: Clean up and refactor CacheLinq...

GitHub user gurustron opened a pull request: https://github.com/apache/ignite/pull/2226 IGNITE-5532 .NET: Clean up and refactor CacheLinqTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/gurustron/ignite feature/IGNITE-5532

[jira] [Created] (IGNITE-5675) Add ability to detect and report anomalities

Yakov Zhdanov created IGNITE-5675: - Summary: Add ability to detect and report anomalities Key: IGNITE-5675 URL: https://issues.apache.org/jira/browse/IGNITE-5675 Project: Ignite Issue Type:

[GitHub] ignite pull request #2225: Ignite gg 12390

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2225 Ignite gg 12390 PR for tests run on TC You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12390 Alternatively

[jira] [Created] (IGNITE-5672) Report contended cache keys if any

Yakov Zhdanov created IGNITE-5672: - Summary: Report contended cache keys if any Key: IGNITE-5672 URL: https://issues.apache.org/jira/browse/IGNITE-5672 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-5671) Collect cache SQL query stats

Yakov Zhdanov created IGNITE-5671: - Summary: Collect cache SQL query stats Key: IGNITE-5671 URL: https://issues.apache.org/jira/browse/IGNITE-5671 Project: Ignite Issue Type: Sub-task

Supported and Unsupported SQL

Igniters, Vladimir pointed out that PostgreSQL has a very detailed list of supported and unsupported features: https://www.postgresql.org/docs/devel/static/features.html I think we can borrow a few things from this format: 1. Have a very detailed documented list of all the

[GitHub] ignite pull request #2224: Ignite 1.7

GitHub user ntikhonov opened a pull request: https://github.com/apache/ignite/pull/2224 Ignite 1.7 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.7.9-p1.b1 Alternatively you can review and apply

[jira] [Created] (IGNITE-5670) Collect high level API calls stats

Yakov Zhdanov created IGNITE-5670: - Summary: Collect high level API calls stats Key: IGNITE-5670 URL: https://issues.apache.org/jira/browse/IGNITE-5670 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-5669) Gather stats for communication queues sizes per node

Yakov Zhdanov created IGNITE-5669: - Summary: Gather stats for communication queues sizes per node Key: IGNITE-5669 URL: https://issues.apache.org/jira/browse/IGNITE-5669 Project: Ignite

[jira] [Created] (IGNITE-5668) Gather stats for communication messages

Yakov Zhdanov created IGNITE-5668: - Summary: Gather stats for communication messages Key: IGNITE-5668 URL: https://issues.apache.org/jira/browse/IGNITE-5668 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-5666) Gather time statistics for user objects (de)serialization

Yakov Zhdanov created IGNITE-5666: - Summary: Gather time statistics for user objects (de)serialization Key: IGNITE-5666 URL: https://issues.apache.org/jira/browse/IGNITE-5666 Project: Ignite

[jira] [Created] (IGNITE-5665) Implement histogram-like functionality to gather time stats on different operations

Yakov Zhdanov created IGNITE-5665: - Summary: Implement histogram-like functionality to gather time stats on different operations Key: IGNITE-5665 URL: https://issues.apache.org/jira/browse/IGNITE-5665

Re: Support for starting transaction in another thread IGNITE-4887

So, desired behavior is the following: when some thread evaluates tx operation's secured scope, other threads should be locked and then released with return after first thread has finished evaluating secured scope ? пн, 3 июл. 2017 г. в 17:12, Yakov Zhdanov : > Yes, feel

[jira] [Created] (IGNITE-5664) Implement self-check facilities for Ignite

Yakov Zhdanov created IGNITE-5664: - Summary: Implement self-check facilities for Ignite Key: IGNITE-5664 URL: https://issues.apache.org/jira/browse/IGNITE-5664 Project: Ignite Issue Type:

Re: JIRA Access - Ignite

Welcome! Added you to the list. — Denis > On Jul 2, 2017, at 11:11 PM, Ankur Kumar wrote: > > ankurkuma...@gmail.com is my JIRA Id. Please grant the permission. > > On Tue, Jun 27, 2017 at 2:16 PM, Alexey Kuznetsov > wrote: > >> Hi Ankur, >>

[jira] [Created] (IGNITE-5663) ODBC: Few consecutive inserts lead to exception

Evgenii Zhuravlev created IGNITE-5663: - Summary: ODBC: Few consecutive inserts lead to exception Key: IGNITE-5663 URL: https://issues.apache.org/jira/browse/IGNITE-5663 Project: Ignite

Re: Ignite Teamcity email notifications

Dmitriy P., The list has been created. Here is a response from ASF: As requested by you, the following mailing list has been created: c...@ignite.apache.org Moderators: dma...@apache.org ,dsetrak...@apache.org

[jira] [Created] (IGNITE-5662) Primary index name should contain type ID or name

Alexey Goncharuk created IGNITE-5662: Summary: Primary index name should contain type ID or name Key: IGNITE-5662 URL: https://issues.apache.org/jira/browse/IGNITE-5662 Project: Ignite

Re: Custom string encoding

Agree with Valya on the system-wide default. We need to have it. Also, are we certain that the encoding will provide 1-byte length for UTF-8 for different languages? Would be nice to test it to confirm, as it has a potential to decrease the Ignite storage space by 2x in certain cases. D. On

[jira] [Created] (IGNITE-5661) ignite.NET serialization failed when entity has property with IList and equals to null

Chris Wang created IGNITE-5661: -- Summary: ignite.NET serialization failed when entity has property with IList and equals to null Key: IGNITE-5661 URL: https://issues.apache.org/jira/browse/IGNITE-5661

[jira] [Created] (IGNITE-5660) ignite.NET serialization failed when entity has property with IList and equals to null

Chris Wang created IGNITE-5660: -- Summary: ignite.NET serialization failed when entity has property with IList and equals to null Key: IGNITE-5660 URL: https://issues.apache.org/jira/browse/IGNITE-5660

Re: Support for starting transaction in another thread IGNITE-4887

So i need to put new lock mechanism to* all* transaction operations ? If so, don't we need additional ticket for this ?(for example sub ticket for my original one) пн, 3 июл. 2017 г. в 16:59, Yakov Zhdanov : > Disagree. Currently transaction is bound to a thread and if user

Re: Support for starting transaction in another thread IGNITE-4887

Disagree. Currently transaction is bound to a thread and if user tries to pass it over to another thread this would be a contract violation. Your ticket will make inter-thread transitions allowed. --Yakov

Re: Support for starting transaction in another thread IGNITE-4887

It is a global scope) Now multiple threads can commit transaction and it will lead to exception. It doesn't refer to my ticket only, but for a current transaction implementation. пн, 3 июл. 2017 г. в 16:53, Yakov Zhdanov : > What separate ticket do you mean here? I think

[jira] [Created] (IGNITE-5659) BinaryMarshaller loads class with local classloader even if it excluded in Configuration

Nikolay Izhikov created IGNITE-5659: --- Summary: BinaryMarshaller loads class with local classloader even if it excluded in Configuration Key: IGNITE-5659 URL: https://issues.apache.org/jira/browse/IGNITE-5659

Re: Support for starting transaction in another thread IGNITE-4887

What separate ticket do you mean here? I think this is the scope of the original one. --Yakov 2017-07-03 16:39 GMT+03:00 ALEKSEY KUZNETSOV : > I've go a test, which illustrates transaction commit fail when multiple > threads try to commit. As i said, it happenes in

Re: Support for starting transaction in another thread IGNITE-4887

I've go a test, which illustrates transaction commit fail when multiple threads try to commit. As i said, it happenes in mvcc stage. So we should create a special lock mechanism for all transaction methods. In a separate ticket. пн, 3 июл. 2017 г. в 16:26, Yakov Zhdanov : >

Re: Support for starting transaction in another thread IGNITE-4887

>Consider thread *Th1* started transaction *Tx1*, done some actions, and is >calling commit (GridNearTxLocal#commit -> commitNearTxLocalAsync). And >concurrently thread *Th2 *is calling the same commit on* Tx1*. Alexey, this looks weird to me. IMO, if we talk about proper implementation you

Re: Support for starting transaction in another thread IGNITE-4887

Lock is put by cache adapter. Now its clear пн, 3 июл. 2017 г. в 15:14, ALEKSEY KUZNETSOV : > Consider thread *Th1* started transaction *Tx1*, done some actions, and > is calling commit (GridNearTxLocal#commit -> commitNearTxLocalAsync). And > concurrently thread *Th2

abbrevation rules plugin

Igntrs! There is a plugin , mentioned in Abbreviation Rules page that performs on-the-fly check.Is somebody going to add it some day? -- *Best Regards,* *Kuznetsov Aleksey*

Re: distributed transaction of non-single coordinator

Yakov, I have couple of questions regarding tests proposal.Thx пт, 30 июн. 2017 г. в 19:17, ALEKSEY KUZNETSOV : > Thanks! Do you think all test scenarios results, presented in table(in > ticket comments) , are acceptable ? > > пт, 30 июн. 2017 г., 18:28 Yakov Zhdanov

Support for starting transaction in another thread IGNITE-4887

Consider thread *Th1* started transaction *Tx1*, done some actions, and is calling commit (GridNearTxLocal#commit -> commitNearTxLocalAsync). And concurrently thread *Th2 *is calling the same commit on* Tx1*. Now, if you look into code : public IgniteInternalFuture commitNearTxLocalAsync() {

[jira] [Created] (IGNITE-5658) Optimizations for data streamer

Yakov Zhdanov created IGNITE-5658: - Summary: Optimizations for data streamer Key: IGNITE-5658 URL: https://issues.apache.org/jira/browse/IGNITE-5658 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-5657) Web Console: add apropriate placeholder in case if no columns are selected in table

Pavel Konstantinov created IGNITE-5657: -- Summary: Web Console: add apropriate placeholder in case if no columns are selected in table Key: IGNITE-5657 URL: https://issues.apache.org/jira/browse/IGNITE-5657

Re: Zookeeper Discovery SPI & external IP address in AWS

My point is that communication SPI should put both address types to its attributes to share - private and addresses processed by a resolver. --Yakov

Re: IGNITE-4901 (Decrease logging level for DataStremer retry)

Alexey, To be more exact Ignite should fail the update only if affinity mapping changes and only for the case when allowOverwrite is false. Please share the PR and we will review it. --Yakov

[GitHub] ignite pull request #2223: Ignite gg 4901

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

[GitHub] ignite pull request #2204: IGNITE-5279

Github user alexpaschenko closed the pull request at: https://github.com/apache/ignite/pull/2204 --- 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: [Review] IGNITE-4648: IgniteInternalTx.prepare() does not wait for async operations to complete

I added test as Yakov said, here is CI only test method added, without bugfix: http://ci.ignite.apache.org/viewLog.html?buildId=694784=Ignite20Tests_RunAll=buildResultsDiv and with bugfix: http://ci.ignite.apache.org/viewLog.html?buildId=695030=Ignite20Tests_RunAll=buildResultsDiv 2017-05-03

[GitHub] ignite pull request #2222: Ignite gg 4901

Github user kukushal closed the pull request at: https://github.com/apache/ignite/pull/ --- 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 #2222: Ignite gg 4901

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

Re: JIRA Access - Ignite

ankurkuma...@gmail.com is my JIRA Id. Please grant the permission. On Tue, Jun 27, 2017 at 2:16 PM, Alexey Kuznetsov wrote: > Hi Ankur, > > What is your JIRA ID? > > On Tue, Jun 27, 2017 at 3:42 PM, Ankur Kumar > wrote: > > > I can access Apache