Re: 1.5.final

The fix for https://issues.apache.org/jira/browse/IGNITE-2200 has been merged to ignite-1.5​

Re: 1.5.final

Hi Igniters We've great progress and only two outstanding issues prevents to release: IGNITE-2252 Add support for cache sql schema in REST topology command IGNITE-2175 Not valid exceptions in case when example can't works with remote node started

[GitHub] ignite pull request: ignite-2175

GitHub user avinogradovgg opened a pull request: https://github.com/apache/ignite/pull/371 ignite-2175 You can merge this pull request into a Git repository by running: $ git pull https://github.com/avinogradovgg/ignite ignite-2175-2 Alternatively you can review and apply

[GitHub] ignite pull request: IGNITE-2228 .NET: Ensure async Task can be ca...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/370 IGNITE-2228 .NET: Ensure async Task can be cancelled. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-2228

[GitHub] ignite pull request: ignite-2175

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

Got it. Looks like this is the only remaining issue. Please let us know here once you fix it, so we could start voting on the final release. On Wed, Dec 23, 2015 at 9:22 AM, Alexey Kuznetsov wrote: > No, this is not old issue, new cache configuration property "SQL

Re: 1.5.final

The fix for https://issues.apache.org/jira/browse/IGNITE-2175 has been merged to ignite-1.5​ On Wed, Dec 23, 2015 at 4:30 PM, Alexey Kuznetsov wrote: > I think "IGNITE-2252 Add support for cache sql schema in REST topology > command" will be fixed tomorrow in first half

[GitHub] ignite pull request: IGNITE-2168 Examples should destroy created c...

GitHub user VladimirErshov opened a pull request: https://github.com/apache/ignite/pull/372 IGNITE-2168 Examples should destroy created caches: SpringBeanExample fails after CacheBinaryAutoStoreExample IGNITE-2168 Examples should destroy created caches: SpringBeanExample

Re: 1.5.final

No, this is not old issue, new cache configuration property "SQL schema" was merged into ignite-1.5 two days ago. I would like to fix in ignite-1.5 in order to be able to execute SQL queries from Ignite console against ignite-1.5 cluster. New "SQL schema" cache configuration property

Re: Dynamic caches creation

Cos, In ignite-1.5 we introduced new binary marshaller. And now you could load data into cache without having POJO classes on server nodes. Just describe them as JdbcTypes in CacheJdbcPojoStoreFactory. The only thing that should be predefined on node start - is a data source(s), but I believe

Re: Dynamic caches creation

Let me try to restate what I've said earlier. - I have a running cluster - I want to create a new cache, configuration of which is totally unknown beforehand. Would be nice if I can do it by executing some custom java code from a client node - I want to be able to load POJO model classes

Re: Dynamic caches creation

Yup, that makes a lot of sense. I've seen the conversation about the marshaller, but somehow I blinded it off. Lemme check more on this Appreciate the pointer! Cos On Thu, Dec 24, 2015 at 07:28AM, Alexey Kuznetsov wrote: > Cos, > > In ignite-1.5 we introduced new binary marshaller. > And now

[jira] [Created] (IGNITE-2254) Need append nodeId for sql-query command in REST API

Andrey Novikov created IGNITE-2254: -- Summary: Need append nodeId for sql-query command in REST API Key: IGNITE-2254 URL: https://issues.apache.org/jira/browse/IGNITE-2254 Project: Ignite

[GitHub] ignite pull request: IGNITE-2252 Add support for cache sql schema ...

GitHub user nva opened a pull request: https://github.com/apache/ignite/pull/374 IGNITE-2252 Add support for cache sql schema in REST topology command You can merge this pull request into a Git repository by running: $ git pull https://github.com/nva/ignite ignite-2252

[GitHub] ignite pull request: Ignite 2032

GitHub user VladimirErshov opened a pull request: https://github.com/apache/ignite/pull/369 Ignite 2032 IGNITE-2032 Filters passed to ScanQuery are not redeployed when originating from a client node added undeploy for client nodes. You can merge this pull request into a Git

[GitHub] ignite pull request: ignite-2175

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

[jira] [Created] (IGNITE-2253) Refactoring fields on cluster page

Dmitriyff created IGNITE-2253: - Summary: Refactoring fields on cluster page Key: IGNITE-2253 URL: https://issues.apache.org/jira/browse/IGNITE-2253 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-2252) Add support for cache sql schema in REST topology command

Alexey Kuznetsov created IGNITE-2252: Summary: Add support for cache sql schema in REST topology command Key: IGNITE-2252 URL: https://issues.apache.org/jira/browse/IGNITE-2252 Project: Ignite

[GitHub] ignite pull request: IGNITE-2200 - Fixed deployment and added a te...

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/367 IGNITE-2200 - Fixed deployment and added a test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2200

Re: Dynamic caches creation

What if I don't know the configuration in advance? Doesn't it mean that I would have to restart the nodes whenever a new cache is configured and needs to be added to the cluster? Cos On Tue, Dec 22, 2015 at 10:37PM, Dmitriy Setrakyan wrote: > Cos, > > As far as schema-on-read, you can set all

Re: Dynamic caches creation

Cos, I am confused. What is the behavior you would like to see? On Wed, Dec 23, 2015 at 12:01 AM, Konstantin Boudnik wrote: > What if I don't know the configuration in advance? Doesn't it mean that I > would have to restart the nodes whenever a new cache is configured and >