[jira] [Created] (IGNITE-3617) Implement support for "Local node" mode on SQL screen

Alexey Kuznetsov created IGNITE-3617: Summary: Implement support for "Local node" mode on SQL screen Key: IGNITE-3617 URL: https://issues.apache.org/jira/browse/IGNITE-3617 Project: Ignite

Re: Multi-cache transactions & persistent store

Hi Igor, In a multi-cache transaction there can several different stores involved, that's why store is not considered to be self-contained. That's why transaction callbacks moved to a separate entity - store session listener. Can you please clarify how do you suggest to use Transaction for this?

Re: Use cases for Ignite

On Sun, Jul 31, 2016 at 11:50 PM, pooja3490 wrote: > Hi, > > I wanted to know that in use case where we need in-memory big data for > on-the-fly computation, does Ignite gives better performance as compared to > kdb (which is also an in-memory database)? > > As far as I

Re: Ignite 2.0 tasks/roadmap

On Mon, Aug 1, 2016 at 3:46 AM, Yakov Zhdanov wrote: > One more point. > > I insist on stop using marshaller and meta caches but switch to spreading > this info via custom discovery events. > Do we have a ticket explaining why this needs to be done? > > --Yakov > >

Re: All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

On Mon, Aug 1, 2016 at 10:01 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Dmitriy, > > The question is how do you calculate the value of the hashCode? Do you want > it to be specified explicitly in INSERT statement? > I think optionally we should allow to specify hashCode as part

[GitHub] ignite pull request #914: ignite-1.6.4

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

Re: IGNITE-2294 implementation details

Ok, I think you don't really understand what public API really is, so let me clarify. What you have described are all internal classes, public API is what end user will see and work with, like Ignite, IgniteCache, QueryCursor, etc... All the internal changes do not require any special discussion,

Re: All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

Dmitriy, The question is how do you calculate the value of the hashCode? Do you want it to be specified explicitly in INSERT statement? 2016-08-01 19:47 GMT+03:00 Dmitriy Setrakyan : > Alex, > > In your case, why not just explicitly set hashcode every time you create an >

Re: IGNITE-2294 implementation details

Alexey, can you attach this document to the ticket, or better yet, just copy it there? On Mon, Aug 1, 2016 at 8:14 AM, Alexander Paschenko < alexander.a.pasche...@gmail.com> wrote: > Guys, > > Here's documented version of current API changes - it's quite modest > https://goo.gl/Y6Cv1b > > - Alex

Re: All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

Alex, In your case, why not just explicitly set hashcode every time you create an object? There is BinaryObjectBuilder.hashCode(...) method. D. On Mon, Aug 1, 2016 at 7:42 AM, al.psc wrote: > Guys, > > It seems like this problem has become an important one

RE: All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

Guys, It seems like this problem has become an important one once again. In the course of working on https://issues.apache.org/jira/browse/IGNITE-2294 (DML support) there's need to support binary marshaller. And, although we can build just BinaryObject and put it to cache, without adequate hash

Re: IGNITE-2294 implementation details

Guys, Here's documented version of current API changes - it's quite modest https://goo.gl/Y6Cv1b - Alex 2016-07-28 20:34 GMT+03:00 Alexander Paschenko : > Sergi, > > OK, I've done it as you said, thanks. > Now working on binary marshaller support. > > - Alex > >

[GitHub] ignite pull request #913: IGNITE-3138 - IgniteDataStreamer: failures are not...

GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/913 IGNITE-3138 - IgniteDataStreamer: failures are not shown on the strea… …ming side You can merge this pull request into a Git repository by running: $ git pull

Re: Ignite 1.7 RELEASE_NOTES

Thanks Vladimir, .NET part looks ok to me. On Mon, Aug 1, 2016 at 2:36 PM, Vladimir Ozerov wrote: > Folks, > > I updated release notes a bit. Please review my changes. > > Vladimir. > > On Mon, Aug 1, 2016 at 2:17 PM, Igor Sapego wrote: > > > C++

Re: Ignite 1.7 RELEASE_NOTES

Folks, I updated release notes a bit. Please review my changes. Vladimir. On Mon, Aug 1, 2016 at 2:17 PM, Igor Sapego wrote: > C++ features: > * Added support for distributed joins in SqlQuery and SqlFieldsQuery. > * Serialization and deserialization performance

Re: Ignite 1.7 RELEASE_NOTES

C++ features: * Added support for distributed joins in SqlQuery and SqlFieldsQuery. * Serialization and deserialization performance improved. ODBC features: * Added support for the numeric type (SQL_NUMERIC_STRUCT). Best Regards, Igor On Mon, Aug 1, 2016 at 1:59 PM, Pavel Tupitsyn

[GitHub] ignite pull request #911: Ignite 3590

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

Re: Ignite 1.7 RELEASE_NOTES

Noteworthy .NET changes: * User-defined AffinityFunction * ASP.NET Output Cache provider * .NET configuration in Apache.Ignite.exe * Distributed joins in SQL and LINQ * Forward Java output to the .NET console * Add Java stack trace on .NET side in IgniteException.InnerException * Move examples

Re: Ignite 2.0 tasks/roadmap

One more point. I insist on stop using marshaller and meta caches but switch to spreading this info via custom discovery events. --Yakov 2016-07-27 19:57 GMT+03:00 Dmitriy Setrakyan : > On Wed, Jul 27, 2016 at 11:36 AM, Yakov Zhdanov > wrote: > > >

Ignite 1.7 RELEASE_NOTES

Igniters, RELEASE_NOTES.txt in ignite-1.7 branch does not look complete to me. There are likely more noteworthy changes since 1.6. Let's discuss the changes to be included in release notes and fix them. Please reply to this email with your proposals. Pavel.

[GitHub] ignite pull request #910: Ignite 2310

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

[GitHub] ignite pull request #857: Ignite 2310 Lock cache partition for affinityRun/a...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/857 --- 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: Multi-cache transactions & persistent store

Igor, you factory should return the same instance for all caches started locally. This way Ignite should call sessionEnd() once. Can you please check? --Yakov 2016-07-30 4:40 GMT+03:00 Igor Rudyak : > Hi guys, > > Playing with Ignite multi-cache transactions(transactions

[jira] [Created] (IGNITE-3616) Drop failed nodes from topology after a configured timeout

Alexey Goncharuk created IGNITE-3616: Summary: Drop failed nodes from topology after a configured timeout Key: IGNITE-3616 URL: https://issues.apache.org/jira/browse/IGNITE-3616 Project: Ignite

Re: Failed to wait for initial partition map exchange

The ticket is created: https://issues.apache.org/jira/browse/IGNITE-3616 2016-07-15 1:51 GMT+03:00 Alexey Goncharuk : > Alexey, I like the idea in general, but killing non-responsive nodes seems >> a bit drastic to me. How about this approach: >> >> - print out

[GitHub] ignite pull request #753: IGNITE-1690 : Re-enabled test.

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

[jira] [Created] (IGNITE-3615) Failed test: IgniteCacheQueryNodeRestartDistributedJoinSelfTest.testRestartsBroadcast

Vladimir Ozerov created IGNITE-3615: --- Summary: Failed test: IgniteCacheQueryNodeRestartDistributedJoinSelfTest.testRestartsBroadcast Key: IGNITE-3615 URL: https://issues.apache.org/jira/browse/IGNITE-3615

[jira] [Created] (IGNITE-3614) Failed test: CacheContinuousQueryFailoverTxReplicatedSelfTest.testUpdatePartitionCounter

Vladimir Ozerov created IGNITE-3614: --- Summary: Failed test: CacheContinuousQueryFailoverTxReplicatedSelfTest.testUpdatePartitionCounter Key: IGNITE-3614 URL: https://issues.apache.org/jira/browse/IGNITE-3614

[jira] [Created] (IGNITE-3613) IGFS: IgfsImpl.size() doesn't take secondary file system in count.

Vladimir Ozerov created IGNITE-3613: --- Summary: IGFS: IgfsImpl.size() doesn't take secondary file system in count. Key: IGNITE-3613 URL: https://issues.apache.org/jira/browse/IGNITE-3613 Project:

[jira] [Created] (IGNITE-3612) Remove IgniteAsyncSupport,

Vladimir Ozerov created IGNITE-3612: --- Summary: Remove IgniteAsyncSupport, Key: IGNITE-3612 URL: https://issues.apache.org/jira/browse/IGNITE-3612 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-3611) IGFS: Merge listPaths and listFiles operations.

Vladimir Ozerov created IGNITE-3611: --- Summary: IGFS: Merge listPaths and listFiles operations. Key: IGNITE-3611 URL: https://issues.apache.org/jira/browse/IGNITE-3611 Project: Ignite Issue