Fwd: When will Ignite support cross-cache SQL joins?

Folks, Are ad-hoc queries already available in master? -Val -- Forwarded message -- From: ght230 Date: Mon, Feb 15, 2016 at 6:09 AM Subject: When will Ignite support cross-cache SQL joins? To: u...@ignite.apache.org I had learned that in version 1.5, Ignite

Re: NoopSwapSpaceSpi and dynamically started caches

Probably I can handle this ticket, but I want to clarify one thing. Suppose dynamic cache with enabled swap should be partitioned between two nodes with backups=1. First node started with FileSwapSpaceSpi, second with NoopSwapSpaceSpi. How cache should start in this case? On Mon, Feb 15, 2016

Re: Grid behavior at key deserialization failure during rebalancing

Anton, I am not sure why we would deserialize on the server side with Binary Marshaller. The data should remain in binary form. Do you know if we have a test for it? Thanks, D. On Mon, Feb 15, 2016 at 1:20 AM, Anton Vinogradov wrote: > Dmitriy, > > Key can be

[GitHub] ignite pull request: IGNITE-2627: Removed OdbcNioParser. Using Gri...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/485 IGNITE-2627: Removed OdbcNioParser. Using GridBufferedParser for message separation. Message parsing moved to OdbcNioListener. You can merge this pull request into a Git repository by running:

[GitHub] ignite pull request: Ignite 2521 TMP (not for merge)

GitHub user ashutakGG opened a pull request: https://github.com/apache/ignite/pull/484 Ignite 2521 TMP (not for merge) TMP PR You can merge this pull request into a Git repository by running: $ git pull https://github.com/ashutakGG/incubator-ignite ignite-2521-tmp-good-set

[GitHub] ignite pull request: ignite-2325 - Fixing assertion on prepare fut...

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

Remove GridBoundedConcurrentLinkedHashMap and replace its usages with ConcurrentLinkedHashMap

Hi Konstantin, I've shared my thoughts on your questions. Yakov, as a creator of the ticket, please share your view on whether these changes are really needed or not. -- Denis Forwarded Message Subject:Re: Hello Date: Mon, 15 Feb 2016 15:08:25 +0300 From:

[jira] [Created] (IGNITE-2654) Protocol optimization for GridNearLockRequest/Response

Ilya Lantukh created IGNITE-2654: Summary: Protocol optimization for GridNearLockRequest/Response Key: IGNITE-2654 URL: https://issues.apache.org/jira/browse/IGNITE-2654 Project: Ignite

[jira] [Created] (IGNITE-2653) .Net: StoreExample failed when running with remote nodes

Vasilisa Sidorova created IGNITE-2653: -- Summary: .Net: StoreExample failed when running with remote nodes Key: IGNITE-2653 URL: https://issues.apache.org/jira/browse/IGNITE-2653 Project: Ignite

Re: Ignite components deserialization

Yes, thanks, already working on it. The reason was: Ignite experts decided, that there should be no case for Ignite to be deserialized outside of IgniteThread. On Sat, Feb 13, 2016 at 2:30 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Folks, > > I reopened the ticket where

[GitHub] ignite pull request: IGNITE-2652: Fix for the QueryFieldsRow::GetN...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/483 IGNITE-2652: Fix for the QueryFieldsRow::GetNext. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-2652 Alternatively you

[jira] [Created] (IGNITE-2652) CPP: The throwing version of the QueryFieldsRow::GetNext() can't be used.

Igor Sapego created IGNITE-2652: --- Summary: CPP: The throwing version of the QueryFieldsRow::GetNext() can't be used. Key: IGNITE-2652 URL: https://issues.apache.org/jira/browse/IGNITE-2652 Project:

[jira] [Created] (IGNITE-2651) Table name inference

Pavel Tupitsyn created IGNITE-2651: -- Summary: Table name inference Key: IGNITE-2651 URL: https://issues.apache.org/jira/browse/IGNITE-2651 Project: Ignite Issue Type: Sub-task

Re: NoopSwapSpaceSpi and dynamically started caches

I've created a newbie issue for that: https://issues.apache.org/jira/browse/IGNITE-2650. -- Artem -- On Wed, Feb 10, 2016 at 8:53 PM, Dmitriy Setrakyan wrote: > Artem, > > I like the option with proper exception in case if a dynamic cache is > started with swap enabled

[jira] [Created] (IGNITE-2650) Ignite should throw an exception on start of dynamic cache with swap if Ignite uses NoopSwapSpaceSpi

Artem Shutak created IGNITE-2650: Summary: Ignite should throw an exception on start of dynamic cache with swap if Ignite uses NoopSwapSpaceSpi Key: IGNITE-2650 URL:

Re: Hello

Hi all. Could please someone review my comment to https://issues.apache.org/jira/browse/IGNITE-1783 It's easy to make a patch, but this will lead to longer arguments list in some places. Is it ok? On Tue, Feb 9, 2016 at 3:11 PM, Vladimir Ozerov wrote: > Konstantin, > >

[jira] [Created] (IGNITE-2649) Ignition.localIgnite() unreliable under Gateways and cause wrong components deserialization.

Vladimir Ershov created IGNITE-2649: --- Summary: Ignition.localIgnite() unreliable under Gateways and cause wrong components deserialization. Key: IGNITE-2649 URL:

[GitHub] ignite pull request: IGNITE-1630 Language Integrated Queries in ca...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/482 IGNITE-1630 Language Integrated Queries in cache (LINQ) You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1630

Re: Grid behavior at key deserialization failure during rebalancing

Dmitriy, Key can be undeserializable during rebalancing because of many reasons. For example, 1) It was serialized with errors 2) Deserialization cause error 3) It based on classes unavailable at node trying to deserialize it Third is the most possible case. On Sat, Feb 13, 2016 at 3:44 AM,

[GitHub] ignite pull request: IGNITE-2597 added socket support

GitHub user Dmitriyff opened a pull request: https://github.com/apache/ignite/pull/481 IGNITE-2597 added socket support You can merge this pull request into a Git repository by running: $ git pull https://github.com/Dmitriyff/ignite ignite-2597 Alternatively you can review

[GitHub] ignite pull request: Ignite 2598

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