Re: Null cache names

Denis, PR is created. https://issues.apache.org/jira/browse/IGNITE-5083 for review. We will have to find a good solution to "externalize" the default cache name in future, as Vladimir suggested. As Igor pointed out, probably for memcached too.I'll create another JIRA issue for that. Roman

[GitHub] ignite pull request #1874: IGNITE-5083: Add default cache for Redis.

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/1874 IGNITE-5083: Add default cache for Redis. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-5083 Alternatively you can

Re: Cluster metrics - review for PageMemory

Is there a way to provide such metrics for a specific memory policy? On Tue, Apr 25, 2017 at 4:53 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Igniters, > > Since we moved to the PageMemory architecture, several ClusterMetrics > methods became questionable, so I would like to

Re: Improve binary enum handling

Vova, I am not sure I am qualified to propose such a design, but I would like to fully understand your proposal. Can you please suggest how a user would use an enum-based query, after having specified an enum in the CREATE TABLE command, as you suggested? D. On Tue, Apr 25, 2017 at 3:17 PM,

Re: Ignite ML, DSL/Scripting (IGNITE-5065)

Folks, Isn’t it to early to dig into DSL implementation? I would take this path only after Ignite supports basic algorithms used for ML and predictive analysis so that people can use it somehow. Then depending on a feedback we might need to start on this task. — Denis > On Apr 25, 2017, at

Re: Apache Ignite 2.0 Release

Alex G., Would you complete the review of IGNITE-4539 and merge the changes? — Denis > On Apr 25, 2017, at 6:33 PM, Roman Shtykh wrote: > > I would also like to include IGNITE-4539. Its implementation is finished. > Roman > >On Wednesday, April 26, 2017 1:59

[jira] [Created] (IGNITE-5083) Add default cache for Redis

Roman Shtykh created IGNITE-5083: Summary: Add default cache for Redis Key: IGNITE-5083 URL: https://issues.apache.org/jira/browse/IGNITE-5083 Project: Ignite Issue Type: Task

Re: Apache Ignite 2.0 Release

I would also like to include IGNITE-4539. Its implementation is finished. Roman On Wednesday, April 26, 2017 1:59 AM, Vladimir Ozerov wrote: Igniters, We are almost there. Outstanding issues which I hope we will be able to resolve quickly: 1) Hibernate 5 support

Re: BinaryObjectImpl.deserializeValue with specific ClassLoader

Nick, Have you tried implementing delegating classloader and set it using IgniteConfiguration.setClassLoader() ? This should solve your problem without any API changes on Ignite's side. 2017-04-25 22:42 GMT+03:00 npordash : > Hi Denis, Val, > > Please refer to my initial

Re: BinaryObjectImpl.deserializeValue with specific ClassLoader

Hi Denis, Val, Please refer to my initial inquiry on the user forum for full context as I think that was lost while cross-posting to here: http://apache-ignite-users.70518.x6.nabble.com/BinaryObjectImpl-deserializeValue-with-specific-ClassLoader-td12055.html The setting in IgniteConfiguration

Re: Null cache names

Agree, lets move forward with the simplest possible solution for now. Sergi 2017-04-25 13:07 GMT+03:00 Vladimir Ozerov : > Folks, > > I do not think it is legal to add such property to ConnectorConfiguration. > Connector is a generic gateway to cluster resources. It should

Re: Cluster metrics - review for PageMemory

Looks good to me. Sergi 2017-04-25 16:53 GMT+03:00 Alexey Goncharuk : > Igniters, > > Since we moved to the PageMemory architecture, several ClusterMetrics > methods became questionable, so I would like to discuss this before the > release. Currently, ClusterMetrics

Re: Ignite ML, next steps (IGNITE-5029)

It is preferable to avoid hard bindings to some exact scripting engines. If user wants to plug in Groovy we should allow it. As for DSL I believe it is a waste of time. Few years ago it was somewhat popular idea to create DSLs for everything, but no one actually wants to learn new quirky

Re: Ignite ML, DSL/Scripting (IGNITE-5065)

I'm a bit out of the loop with ML and Web console, but Java scripting engines as in JSR-233 are supported in Java 7. You can use JSR-233 API in Web Console, implementation will be in IgniteML module, which requires Java 8 anyways. This way they will be decoupled. Does this work for you? Sergi

Ignite ML, DSL/Scripting (IGNITE-5065)

Hi all! Currently I'm working on adding scripting support for Ignite ML(IGNITE-5065). The basic idea is to provide possibility to create and run some scripts with ML algorithms over Ignite cluster using Ignite ML API and JS/Python as script language. I’ve exchanged several thoughts with Alexey

Re: BinaryObjectImpl.deserializeValue with specific ClassLoader

It’s a good point. Thanks for reminding Val. Nick, please check that the suggested method works for your use case. — Denis > On Apr 25, 2017, at 11:16 AM, Valentin Kulichenko > wrote: > > We allow to provide custom class loader via >

Re: BinaryObjectImpl.deserializeValue with specific ClassLoader

We allow to provide custom class loader via IgniteConfiguration.setClassLoader. If this class loader is ignored during deserialization of cache objects, then I believe it's a bug. -Val On Tue, Apr 25, 2017 at 7:36 PM, Denis Magda wrote: > Nick, > > This deserialization issue

Re: Cluster metrics - review for PageMemory

Personally, Total and Committed metrics look confusing to me. Moreover, looks like they interfere with the rest of the metrics this or that way. So, +1 for the changes proposed by Alex G. — Denis > On Apr 25, 2017, at 6:53 AM, Alexey Goncharuk > wrote: > >

Re: MemoryMetrics interface inconsistencies

Totally agree with all Pavel’s and Vovan's suggestions and concerns, especially, with the following: > 2) MemoryMetrics has methods that modify state, like enableMetrics > and rateTimeInterval > (IgniteCache.metrics() returns a read-only serializable snapshot) > > 3) getSize method returns size

Re: Ignite ML, next steps (IGNITE-5029)

First of all thanks for this advice. And DSL/Scripting update: Actually it's a two separate features. The first is provide scripting from some web ui. I think we could use web-console as ui part and JSR 223 for scripting itself, Nashorn for JS and Jython for Python. And the second feature -

Re: BinaryObjectImpl.deserializeValue with specific ClassLoader

Nick, This deserialization issue is related to cache objects. You will get the same kind of exception if you try to deserialize a cache entry inside of a compute task which class was preloaded using the peer-class-loading feature. Frankly, this is not treated as an issue on Ignite side. We

Re: Apache Ignite 2.0 Release

Igniters, We are almost there. Outstanding issues which I hope we will be able to resolve quickly: 1) Hibernate 5 support [1] 2) Two SQL tickets (2], [3] 3) Two page memory tickets [4], [5] 4) TcpDiscoverySpi.heartbeatsFrequency [6] 5) Prohibit "null" as cache name [7] Most of them are in "Patch

[GitHub] ignite pull request #1873: logging was improved

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1873 logging was improved You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5079 Alternatively you can

[jira] [Created] (IGNITE-5081) SecurityPermissionSetBuilder duplicates permission if it's appended more than once

Valentin Kulichenko created IGNITE-5081: --- Summary: SecurityPermissionSetBuilder duplicates permission if it's appended more than once Key: IGNITE-5081 URL: https://issues.apache.org/jira/browse/IGNITE-5081

[jira] [Created] (IGNITE-5080) SecurityBasicPermissionSet implementation is incomplete

Valentin Kulichenko created IGNITE-5080: --- Summary: SecurityBasicPermissionSet implementation is incomplete Key: IGNITE-5080 URL: https://issues.apache.org/jira/browse/IGNITE-5080 Project: Ignite

[jira] [Created] (IGNITE-5079) Improve debug logging for binary metadata exchange

Sergey Chugunov created IGNITE-5079: --- Summary: Improve debug logging for binary metadata exchange Key: IGNITE-5079 URL: https://issues.apache.org/jira/browse/IGNITE-5079 Project: Ignite

Re: Handling of @AffinityKeyMapped and @QuerySqlField annotations in Cassandra store

I agree. Using @QuerySqlField in Cassandra store seems to be incorrect design decision in the first place. -Val On Tue, Apr 25, 2017 at 2:22 PM, Vladimir Ozerov wrote: > Hi Igor, > > During API stabilization and improvement for Apache Ignite 2.0 we > restricted usage of

[GitHub] ignite pull request #1872: MemoryMetrics interface cleanup, MemoryMetricsImp...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1872 MemoryMetrics interface cleanup, MemoryMetricsImpl split You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1871: ignite-5041 NPE in deadlock detection fixed

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/1871 ignite-5041 NPE in deadlock detection fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-5041 Alternatively

[GitHub] ignite pull request #1800: Obsolete cache metrics removed, test fixed

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1800 --- 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

Handling of @AffinityKeyMapped and @QuerySqlField annotations in Cassandra store

Hi Igor, During API stabilization and improvement for Apache Ignite 2.0 we restricted usage of @AffinityKeyMapped and @QuerySqlField annotations to fields only, because annotations on method level are not supported by BinaryMarshaller (which is default) and goes against our general approach of

Re: Improve binary enum handling

Dima, Sergi, Please propose how are you going to work with enums from SQL perspective without registering them in advance. I already shared my thoughts and provided two examples how this is achieved in MySQL and PostgreSQL. On Tue, Apr 25, 2017 at 3:06 PM, Dmitriy Setrakyan

Re: Improve binary enum handling

Vladimir, can you please share your thoughts here? On Mon, Apr 24, 2017 at 5:21 PM, Sergi Vladykin wrote: > I agree with Dmitriy, it is preferable to have this enum registration > optional. It will be a better user experience. > > Why do we "inevitably" need it? > >

[GitHub] ignite pull request #1870: IGNITE-5077 - Support service security permission...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1870 IGNITE-5077 - Support service security permissions You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5077

[jira] [Created] (IGNITE-5078) Partition lost event is fired only on coordinator when partition loss policy is IGNORE

Alexey Goncharuk created IGNITE-5078: Summary: Partition lost event is fired only on coordinator when partition loss policy is IGNORE Key: IGNITE-5078 URL: https://issues.apache.org/jira/browse/IGNITE-5078

[GitHub] ignite pull request #1856: Ignite 5040

Github user ybabak closed the pull request at: https://github.com/apache/ignite/pull/1856 --- 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-5077) Support service permissions

Dmitry Karachentsev created IGNITE-5077: --- Summary: Support service permissions Key: IGNITE-5077 URL: https://issues.apache.org/jira/browse/IGNITE-5077 Project: Ignite Issue Type: New

[GitHub] ignite pull request #1869: Ignite 3935

Github user alt-freem closed the pull request at: https://github.com/apache/ignite/pull/1869 --- 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 #1869: Ignite 3935

GitHub user alt-freem opened a pull request: https://github.com/apache/ignite/pull/1869 Ignite 3935 Это не PullRequest, в том смысле что задача не выполнена, PR завел просто как площадку для обсуждения и

Re: Null cache names

Folks, I do not think it is legal to add such property to ConnectorConfiguration. Connector is a generic gateway to cluster resources. It should not bother about caches anyhow. What if there are multiple caches in the cluster? What is I want to access "cache A" from Memcached and "cache B" from

[jira] [Created] (IGNITE-5076) Optimization of multi-threaded start nodes in tests

Dmitriy Govorukhin created IGNITE-5076: -- Summary: Optimization of multi-threaded start nodes in tests Key: IGNITE-5076 URL: https://issues.apache.org/jira/browse/IGNITE-5076 Project: Ignite

[GitHub] ignite pull request #1867: incorrect construction of swap files directory pa...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1867 incorrect construction of swap files directory path fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-5075) Implement logical 'cache groups' sharing the same physical caches

Semen Boikov created IGNITE-5075: Summary: Implement logical 'cache groups' sharing the same physical caches Key: IGNITE-5075 URL: https://issues.apache.org/jira/browse/IGNITE-5075 Project: Ignite

[jira] [Created] (IGNITE-5074) Split up asynchronous and synchronous calls in PlatformCompute

Igor Sapego created IGNITE-5074: --- Summary: Split up asynchronous and synchronous calls in PlatformCompute Key: IGNITE-5074 URL: https://issues.apache.org/jira/browse/IGNITE-5074 Project: Ignite

[jira] [Created] (IGNITE-5073) Race between partition exchange process and client cache operations

Semen Boikov created IGNITE-5073: Summary: Race between partition exchange process and client cache operations Key: IGNITE-5073 URL: https://issues.apache.org/jira/browse/IGNITE-5073 Project: Ignite

[jira] [Created] (IGNITE-5072) Move memory metrics to snapshots

Alexey Goncharuk created IGNITE-5072: Summary: Move memory metrics to snapshots Key: IGNITE-5072 URL: https://issues.apache.org/jira/browse/IGNITE-5072 Project: Ignite Issue Type:

Re: MemoryMetrics interface inconsistencies

Can you give an example of such API usage? A piece of code to enable metrics and retrieve a snapshot? On Mon, Apr 24, 2017 at 8:06 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Agree, I overlooked this during the review. However, the changes to fix > this is pretty simple - we just

Re: SQL usability: catalogs, schemas and tables

Vladimir, great suggestions. Can you please make an umbrella ticket with sub-tasks, so we can tackle some of them for 2.1? D. On Mon, Apr 24, 2017 at 5:28 PM, Sergi Vladykin wrote: > Yes, we need to move on making Ignite work as any usual SQL db. > > But please avoid