[jira] [Created] (IGNITE-6376) Web console: Enable task and job events in demo mode by default.

Vasiliy Sisko created IGNITE-6376: - Summary: Web console: Enable task and job events in demo mode by default. Key: IGNITE-6376 URL: https://issues.apache.org/jira/browse/IGNITE-6376 Project: Ignite

[Announcement] Talk: Real-time Data Analysis with Apache Ignite High-Performance In-memory Platform

Hi, I will be making a short presentation at Data Platform Conference Tokyo 2017 on Apache Ignite with emphasis on IoT. Attending is free. Please come if you are in Tokyo. https://ignite.apache.org/events.html#dataplatform-jp Best regards,Roman

Re: Durable Memory and Ignite Persistence Tuning

Ivan, Documented: https://apacheignite.readme.io/v2.1/docs/durable-memory-tuning However, I’m a bit confused with you 6. point regarding the page size calculation. Should Ignite page size be always less than the SSD’s page size

Re: Web Sessions not considered valid by our RequestWrapper - FIX

Ilya, I'm not suggesting to include this code as-is, but rather add tests that for this use case and improve code coverage. Our current test seem to be very artificial and we keep getting issues like this one. I'm open to suggestions here, this can even be done as a separate task if we extend the

Re: Expiry policy for Cache.invoke

Denis, I'm confused by the issue. Do you mean that we can use expiry policy other than the one provided in configuration? How is this possible? Can you point to the code that implements this logic? -Val On Wed, Sep 13, 2017 at 11:29 AM, Dmitriy Setrakyan wrote: > Denis,

Re: [VOTE] Apache Ignite 2.2.0 RC1

Unfortunately, in addition to the minor concern below I’ve stumbled on showstoppers. 1) SQL doesn’t work in Web Console: https://issues.apache.org/jira/browse/IGNITE-6374 2) Some issue with CREATE TABLE’s affinityKey command or DML being use:

[jira] [Created] (IGNITE-6375) CREATE TABLE affinityKey parameter doesn't work as expected

Denis Magda created IGNITE-6375: --- Summary: CREATE TABLE affinityKey parameter doesn't work as expected Key: IGNITE-6375 URL: https://issues.apache.org/jira/browse/IGNITE-6375 Project: Ignite

[jira] [Created] (IGNITE-6374) Web Console SQL doesn't work with 2.2.0 RC1

Denis Magda created IGNITE-6374: --- Summary: Web Console SQL doesn't work with 2.2.0 RC1 Key: IGNITE-6374 URL: https://issues.apache.org/jira/browse/IGNITE-6374 Project: Ignite Issue Type: Bug

Re: [VOTE] Apache Ignite 2.2.0 RC1

Guys, Another point of concern. After building the binaries from sources and starting a node from a terminal ./ignite.sh ../examples/config/example-ignite.xml the node automatically turns off the QUIET mode and the terminal window is swamped by all the sort of noisy INFO logs. The same is

Re: ML Example

Yury, I would add an example for the linear regression too: https://apacheignite.readme.io/docs/ols-multiple-linear-regression Generally, it will be ideally to prepare both the docs and example for every algorithm to be

Re: sql documentation

Serge, I like the proposed format. It reminds me the one chosen by MemSQL which is crystal clear: https://docs.memsql.com/sql-reference/v5.8/sql-reference-overview/ Not 100% sure about “Java Developer Guides” section. Let me contemplate a bit and propose other solutions. — Denis > On Sep 13,

Re: Durable Memory and Ignite Persistence Tuning

That’s exactly the discussion around that documentation. Feel free to add these useful points there or wait while I’ll do this later. — Denis > On Sep 13, 2017, at 12:27 PM, Dmitriy Setrakyan wrote: > > Completely agree with Nikita. Why not add this information here? >

Re: Experimental features - thin client protocol as a first candidate

In first version the protocol version can be “0.1”, 0.2”, etc. Once we are sure the protocol is mature enough it can be stamped with version 1.0. The point is that the versions like 0.x imply that the protocol is not 100% final which is pretty similar but not that loud as the experimental

Re: Durable Memory and Ignite Persistence Tuning

Completely agree with Nikita. Why not add this information here? https://apacheignite.readme.io/docs/durable-memory-tuning D. On Wed, Sep 13, 2017 at 2:54 AM, Nikita Ivanov wrote: > Excellent work on this... This should be expanded and be prominently placed > in our

Re: Experimental features - thin client protocol as a first candidate

Vladimir, As far as the client, I don't think we need to call it experimental. An "experimental" feature sounds like it might explode if you come close :) How about we have client protocol versions instead? Then each Ignite release can announce which protocol versions it is compatible with. D.

[GitHub] ignite pull request #2657: Ignite 2.1.4 p2

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

Re: Expiry policy for Cache.invoke

Denis, I agree that the behavior should be consistent, but you will not find anything about transactions in JCache. To my knowledge, JCache does not have transactions. I would file a ticket about the issue you found, so the community could address it. If you are interested, perhaps you can

Re: ML Example

Hi Akmal, Actually we have two version of k-means local and distributed. And you implemented example of local version. If you want to visualize cluster centers you could use Tracer like this: /for (Vector v:mdl.centers()) Tracer.showAscii(v);/ Unfortunately right now we don`t have good

[jira] [Created] (IGNITE-6373) Create example for local and distributed k-means algorithm

Yury Babak created IGNITE-6373: -- Summary: Create example for local and distributed k-means algorithm Key: IGNITE-6373 URL: https://issues.apache.org/jira/browse/IGNITE-6373 Project: Ignite

[jira] [Created] (IGNITE-6372) .NET: Direct offheap access

Pavel Tupitsyn created IGNITE-6372: -- Summary: .NET: Direct offheap access Key: IGNITE-6372 URL: https://issues.apache.org/jira/browse/IGNITE-6372 Project: Ignite Issue Type: Improvement

[GitHub] ignite pull request #2626: IGNITE-5549 : Fixed situation when mvcc pending q...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2626 ---

ML Example

I am working with the 2.2.0 RC and have built the ML examples and successfully imported them into IntelliJ. I'd like to try a K-Means example, but the online documentation only contains code fragments: https://apacheignite.readme.io/docs/k-means-clustering which I have managed to put together:

[GitHub] ignite pull request #2656: Ignite 6350: Forbid configurations with NOT NULL ...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/2656 Ignite 6350: Forbid configurations with NOT NULL fields and read-through cache store You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-6371) .NET: Thin client example

Pavel Tupitsyn created IGNITE-6371: -- Summary: .NET: Thin client example Key: IGNITE-6371 URL: https://issues.apache.org/jira/browse/IGNITE-6371 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-6370) .NET: Convert ICluster.TopologyVersion to a method

Pavel Tupitsyn created IGNITE-6370: -- Summary: .NET: Convert ICluster.TopologyVersion to a method Key: IGNITE-6370 URL: https://issues.apache.org/jira/browse/IGNITE-6370 Project: Ignite

Re: ContinuousQueryWithTransformer implementation questions - 2

Guys. I'm new in the project so can someone more experienced tell me: What's is wrong with the current implementation of ContinuousQuery? 1. initialQuery is useless - OK, understood. What else is wrong? 2017-09-12 20:02 GMT+03:00 Николай Ижиков : > Vova, > > > Public

[GitHub] ignite pull request #2655: Ignite 1.6.13

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

[jira] [Created] (IGNITE-6369) 2.11 Spark integration has a dependency on Spark's 2.10 library

Hubert Plociniczak created IGNITE-6369: -- Summary: 2.11 Spark integration has a dependency on Spark's 2.10 library Key: IGNITE-6369 URL: https://issues.apache.org/jira/browse/IGNITE-6369 Project:

Re: Specifying schema name with thin JDBC driver

Vova, I think we need to abandon this "schema-name = table name" legacy. It is impossible to explain. Also, I would like to understand the current behavior. When I connect through JDBC, which schema am I connecting to? How do I know which schemas are there? D. On Wed, Sep 13, 2017 at 1:19 AM,

[GitHub] ignite pull request #2636: For testing.

Github user ilantukh closed the pull request at: https://github.com/apache/ignite/pull/2636 ---

[GitHub] ignite pull request #2634: For testing only.

Github user ilantukh closed the pull request at: https://github.com/apache/ignite/pull/2634 ---

Expiry policy for Cache.invoke

Igniters! I noticed a weird behavior regarding expiry policy in Ignite. You can find an example in the attachment. When you call invoke on a cache with configured CacheStore and ExpiryPolicy, then chosen expiry depends on cache's atomicity mode. If cache is atomic, then "creation" expiry timeout

Re: Persistence per memory policy configuration

Can we have separate MemoryPolycy for every CacheGroup? In that case we could auto generate MemoryPolycy based on CacheGroup settings and have a "cache level" persistence settings. We can use some kind of MemoryPolicyTemplate to add default values and even re-use existing MemoryPolicy if all

[jira] [Created] (IGNITE-6368) .NET: Separate interfaces for Ignite and Cache facades for thin client

Vladimir Ozerov created IGNITE-6368: --- Summary: .NET: Separate interfaces for Ignite and Cache facades for thin client Key: IGNITE-6368 URL: https://issues.apache.org/jira/browse/IGNITE-6368

Experimental features - thin client protocol as a first candidate

Igniters, I would propose to add a concept of "experimental feature". Quite often we face a situation when newly created feature has not-so-good API, or tested insufficiently, etc.. Many vendors employ a concept of so-called "experimental" features to mitigate the risks. Examples I am aware of:

[GitHub] ignite pull request #2653: IGNITE-6347: Read unsigned short in GridDhtPartit...

Github user mlipkovich closed the pull request at: https://github.com/apache/ignite/pull/2653 ---

Re: sql documentation

I have done some reorganizing for the SQL documentation. Thanks a lot for the review and proof read. On Wed, 13 Sep 2017 at 01:22, Dmitriy Setrakyan wrote: > Thanks Sergey, I think we should add SQL Syntax section on the left. Also, > please let us know when we can

[jira] [Created] (IGNITE-6365) Wrong EventType and oldValue in RemoteFilter of CQ on not primary node due to reordering after EntryProcessor update

Evgenii Zhuravlev created IGNITE-6365: - Summary: Wrong EventType and oldValue in RemoteFilter of CQ on not primary node due to reordering after EntryProcessor update Key: IGNITE-6365 URL:

Re: Durable Memory and Ignite Persistence Tuning

Excellent work on this... This should be expanded and be prominently placed in our docs/tutorials/javadocs/etc. -- Nikita Ivanov On Wed, Sep 13, 2017 at 12:29 PM, Ivan Rakov wrote: > Folks, > > We had some experience of benchmarking Ignite with persistent store on >

Re: Durable Memory and Ignite Persistence Tuning

> None of them require changing configuration of Ignite or persistent store Disclaimer: this will be true since 2.3. https://issues.apache.org/jira/browse/IGNITE-6182 - memory policy default max size set to 20% of RAM - since 2.2 https://issues.apache.org/jira/browse/IGNITE-5884 - default

Re: Durable Memory and Ignite Persistence Tuning

Folks, We had some experience of benchmarking Ignite with persistent store on SSD. I think we can share some helpful advice. None of them require changing configuration of Ignite or persistent store. *Tuning advice for users* 1) Be prepared for LFS performance decrease after several hours

Re: Web Sessions not considered valid by our RequestWrapper - FIX

Hello Valentin, The application you are probably referring to is user code from Stack Overflow and its license is uncertain. Moreover, this will require depending our tests on spring-mvc and spring-security. If that is acceptable, I could throw together a clean room implementation. But I still

Re: guard() and checkClusterState() checks in Ignite Kernal

Hello Dmitriy, Yes, there is: https://issues.apache.org/jira/browse/IGNITE-6184 Regards, -- Ilya Kasnacheev 2017-09-13 1:46 GMT+03:00 Dmitriy Setrakyan : > Is there a ticket for this change? > > On Tue, Sep 12, 2017 at 4:25 AM, Ilya Kasnacheev < >

[GitHub] ignite pull request #2649: Ignite-gg-12767s

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/2649 ---

[jira] [Created] (IGNITE-6364) .NET: Improve exception message when enumerating entries multiple times in ICacheStore.WriteAll

Pavel Tupitsyn created IGNITE-6364: -- Summary: .NET: Improve exception message when enumerating entries multiple times in ICacheStore.WriteAll Key: IGNITE-6364 URL:

[GitHub] ignite pull request #2640: IGNITE-6345: Wrong message about cluster activati...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2640 ---

Re: [VOTE] Apache Ignite 2.2.0 RC1

Officially cancelling the vote according to found issues. On Wed, Sep 13, 2017 at 8:19 AM, Denis Magda wrote: > How could we miss these binaries? Isn't the release procedure automated > ODBC installers creation? I thought a smoke-testing is done for a final > release

Re: Deprecate IgniteCache.query(Query, IgniteClosure<T,R>)

Val, You are right, generics will not allow us to do that. Sad. On Mon, Sep 11, 2017 at 7:35 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Vova, > > I doubt you'll be able to easily add it directly to ScanQuery because of > generics. Do you have an alternative API in mind? >

Re: Specifying schema name with thin JDBC driver

Valya, Schema name can be specified through Connection.setSchema() method. In the nearest release it would also be possible to specify schema in connection string. E.g. "jdbc:ignite:thin://myHost/*mySchema*". On Mon, Sep 11, 2017 at 10:22 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com>

Re: Persistence per memory policy configuration

Sounds good. But can we see a full example of such configuration? E.g. we have two caches, one in-memory, another persistent. On Wed, Sep 13, 2017 at 10:54 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > I like the idea of having PersistentMemoryPolicy configuration class. >

Re: Persistence per memory policy configuration

I like the idea of having PersistentMemoryPolicy configuration class. Vladimir, Yakov, any objections? 2017-09-13 3:05 GMT+03:00 Denis Magda : > I would go for PersistentMemoryPolicyConfiguration way if it will be > expanded by storage related settings furthers. > > For