Re: Deprecate CacheConfiguration.setIndexedTypes

Exception is thrown for safety if setIndexedTypes is called more than once. Otherwise second call will override the first one and Key1-Value1 will be ignored. The correct code should look like this: setIndexedTypes(Key1.class, Value1.class, Key2.class, Value2.class); Generally, I agree with this

[jira] [Created] (IGNITE-5034) visorcmd: we need to fix cache info visor prints

Pavel Konstantinov created IGNITE-5034: -- Summary: visorcmd: we need to fix cache info visor prints Key: IGNITE-5034 URL: https://issues.apache.org/jira/browse/IGNITE-5034 Project: Ignite

[jira] [Created] (IGNITE-5035) visorcmd doesn't show all new properties that were added in AI 2.0 in CacheConfiguration

Pavel Konstantinov created IGNITE-5035: -- Summary: visorcmd doesn't show all new properties that were added in AI 2.0 in CacheConfiguration Key: IGNITE-5035 URL: https://issues.apache.org/jira/browse/IGNITE-50

Re: Proper collocation of computations and data.

I think the following should be done: - AffinityKeyMapped annotation should be fixed if it's broken (obviously). - There should be a way to specify cache name in addition to key (another annotation?). - Semantics of a job or closure executed with this annotation should be the sam

Re: Deprecate CacheConfiguration.setIndexedTypes

Valya, Normally setters do not throw exceptions. It is perfectly fine to override something. This is how 99% of our configuration works. In this case exception is thrown because indexed types are converted to query entities inside the setter, so the next call to this setter cannot understand what

[jira] [Created] (IGNITE-5036) Disallow @QuerySqlField and @QueryTextField on methods

Vladimir Ozerov created IGNITE-5036: --- Summary: Disallow @QuerySqlField and @QueryTextField on methods Key: IGNITE-5036 URL: https://issues.apache.org/jira/browse/IGNITE-5036 Project: Ignite

[jira] [Created] (IGNITE-5037) Fix broken @AffinityKeyMapped annotation for compute jobs.

Alexei Scherbakov created IGNITE-5037: - Summary: Fix broken @AffinityKeyMapped annotation for compute jobs. Key: IGNITE-5037 URL: https://issues.apache.org/jira/browse/IGNITE-5037 Project: Ignite

Re: Page Memory behavior with default memory policy

Guys, If we have a default of 80% of available memory then just starting few nodes on my laptop will make it hang. This idea does not work until we have a dynamically expandable memory pools. Sergi 2017-04-19 22:20 GMT+03:00 Dmitriy Setrakyan : > Sergey, > > I have responded in the ticket. Can

[GitHub] ignite pull request #1804: IGNITE-4565

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1804 --- 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: Page Memory behavior with default memory policy

This actually will affect only nodes started in a single jvm, but I agree that expandable memory provides better user experience. Let's try to squeeze this change to 2.0. 2017-04-20 12:32 GMT+03:00 Sergi Vladykin : > Guys, > > If we have a default of 80% of available memory then just starting few

Re: Page Memory behavior with default memory policy

Guys, Do we have a ticket for this change? On Thu, Apr 20, 2017 at 1:13 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > This actually will affect only nodes started in a single jvm, but I agree > that expandable memory provides better user experience. Let's try to > squeeze this chan

Re: Page Memory behavior with default memory policy

yes, we do: IGNITE-5024 On Thu, Apr 20, 2017 at 1:23 PM, Vladimir Ozerov wrote: > Guys, > > Do we have a ticket for this change? > > On Thu, Apr 20, 2017 at 1:13 PM, Alexey Goncharuk < > alexey.goncha...@gmail.com> wrote: > > > This actually wi

[jira] [Created] (IGNITE-5038) Add BinaryObject.deserialize(ClassLoader) method

Dmitry Karachentsev created IGNITE-5038: --- Summary: Add BinaryObject.deserialize(ClassLoader) method Key: IGNITE-5038 URL: https://issues.apache.org/jira/browse/IGNITE-5038 Project: Ignite

[GitHub] ignite pull request #1823: Ignite 4799

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

[GitHub] ignite pull request #1836: Ignite 4799

GitHub user abeliak opened a pull request: https://github.com/apache/ignite/pull/1836 Ignite 4799 Do not merge You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4799 Alternatively you can review and ap

[GitHub] ignite pull request #1837: IGNITE-5018 Javadocs in Ignite ML module.

GitHub user oignatenko opened a pull request: https://github.com/apache/ignite/pull/1837 IGNITE-5018 Javadocs in Ignite ML module. - compliance with coding guidelines (rev 17 at https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines) - verified with diffs ove

[GitHub] ignite pull request #1838: Ignite gg 11423 from20

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/1838 Ignite gg 11423 from20 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11423-from20 Alternatively you ca

[GitHub] ignite pull request #1839: IgniteCacheAtomicProtocolTest fix

GitHub user kdudkov opened a pull request: https://github.com/apache/ignite/pull/1839 IgniteCacheAtomicProtocolTest fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite cap-test-fix Alternatively you can re

[jira] [Created] (IGNITE-5039) .NET: Document VC++ requirement

Pavel Tupitsyn created IGNITE-5039: -- Summary: .NET: Document VC++ requirement Key: IGNITE-5039 URL: https://issues.apache.org/jira/browse/IGNITE-5039 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-5040) ML examples

Sergey Kozlov created IGNITE-5040: - Summary: ML examples Key: IGNITE-5040 URL: https://issues.apache.org/jira/browse/IGNITE-5040 Project: Ignite Issue Type: Bug Components: general

Re: Page Memory behavior with default memory policy

Dmitriy, Replied in the ticket. Thanks, Sergey. On Wed, Apr 19, 2017 at 10:20 PM, Dmitriy Setrakyan wrote: > Sergey, > > I have responded in the ticket. Can you please provide the current and the > proposed configuration examples? > > D. > > On Wed, Apr 19, 2017 at 2:34 AM, Sergey Chugunov < >

Re: Performance vs correctness: I vote fore the second

Guys, hope i can add one more example here. Ones we use IgniteAtomicSequence, after topology changes some assertions can be catched due to default AtomicConfiguration i.e. public static final int DFLT_BACKUPS = 0; public static final CacheMode DFLT_CACHE_MODE = PARTITIONED; minimal imp

Re: Performance vs correctness: I vote fore the second

Evgeniy, Good catch! I personally had to explain users several time why they loose data in these cases with default configuration. "AtomicConfiguration.backups = 0" and "CollectionConfiguration.backups = 0" as defaults is nonsense. On Thu, Apr 20, 2017 at 3:27 PM, Evgeniy Stanilovskiy < estanilov

[jira] [Created] (IGNITE-5041) NPE during deadlock detection because cache isn't started on node

Andrey Gura created IGNITE-5041: --- Summary: NPE during deadlock detection because cache isn't started on node Key: IGNITE-5041 URL: https://issues.apache.org/jira/browse/IGNITE-5041 Project: Ignite

[GitHub] ignite pull request #1840: Ignite gg 11423 from20

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/1840 Ignite gg 11423 from20 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11423-from20 Alternatively you ca

Re: Performance vs correctness: I vote fore the second

Yeah, that's a very good point. However, the problem here is that we use single cache for very different structures. For atomics, for example, partitioned cache makes sense (usually with 1 or more backups though). While reentrant locks should always be in replicated cache in my view (or at least by

Re: Performance vs correctness: I vote fore the second

Valya, Why do you think locks should be in REPLICATED cache? It will make their performance so poor, that users are likely to give using them :-) On Thu, Apr 20, 2017 at 4:04 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Yeah, that's a very good point. However, the problem he

[jira] [Created] (IGNITE-5042) Add internal ring wide msg for status check

Alexander Belyak created IGNITE-5042: Summary: Add internal ring wide msg for status check Key: IGNITE-5042 URL: https://issues.apache.org/jira/browse/IGNITE-5042 Project: Ignite Issue Ty

[GitHub] ignite pull request #1841: Ignite 4760#1084

GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/1841 Ignite 4760#1084 - added AccessType parameter in 'threadLocalForCache' - merge HibernateL2CacheNonStrictReadWriteSelfTest and HibernateL2CacheReadWriteSelfTest to HibernateL2CacheStrategySe

[GitHub] ignite pull request #1842: part2node map optimizations

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/1842 part2node map optimizations You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12095 Alternatively you can revi

[jira] [Created] (IGNITE-5043) Support CacheConfiguration.writeBehindCoalescing in .Net

Alexander Belyak created IGNITE-5043: Summary: Support CacheConfiguration.writeBehindCoalescing in .Net Key: IGNITE-5043 URL: https://issues.apache.org/jira/browse/IGNITE-5043 Project: Ignite

[GitHub] ignite pull request #1768: Ignite 4760

Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/1768 --- 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 #1768: Ignite 4760

GitHub user vadopolski reopened a pull request: https://github.com/apache/ignite/pull/1768 Ignite 4760 Added failed test with adding, updating cache. Fixed method threadLocalForCache per-cache thread local. You can merge this pull request into a Git repository by running:

[GitHub] ignite pull request #1841: Ignite 4760#1084

Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/1841 --- 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 #1841: Ignite 4760#1084

GitHub user vadopolski reopened a pull request: https://github.com/apache/ignite/pull/1841 Ignite 4760#1084 - added AccessType parameter in 'threadLocalForCache' - merge HibernateL2CacheNonStrictReadWriteSelfTest and HibernateL2CacheReadWriteSelfTest to HibernateL2CacheStrategy

[GitHub] ignite pull request #1843: Ignite gg 12084

GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/1843 Ignite gg 12084 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12084 Alternatively you can review and app

[jira] [Created] (IGNITE-5044) JVM crash

Sergey Kozlov created IGNITE-5044: - Summary: JVM crash Key: IGNITE-5044 URL: https://issues.apache.org/jira/browse/IGNITE-5044 Project: Ignite Issue Type: Bug Components: general, h

[GitHub] ignite pull request #1844: IGNITE-4477 - Fix IgniteFuture.listen() and Ignit...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1844 IGNITE-4477 - Fix IgniteFuture.listen() and IgniteFuture.chain() semantics You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apach

[GitHub] ignite pull request #1845: IGNITE-4997

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/1845 IGNITE-4997 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4997-2 Alternatively you can review and apply thes

[GitHub] ignite pull request #1697: IGNITE-4849 Review and refactoring the versioned ...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1697 --- 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 feat

[GitHub] ignite pull request #1816: IGNITE-4990 Remove deprecated properties from Fil...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1816 --- 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 feat

[GitHub] ignite pull request #1720: ignite-4523

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

[GitHub] ignite pull request #1846: ignite-4523

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/1846 ignite-4523 Allow distributed SQL query execution over explicit set of partitions. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ascherba

IGNITE-1084 and IGNITE-4760 are ready for review

Hi Semyon! I added AccessType parameter in 'threadLocalForCache'. Merged HibernateL2CacheNonStrictReadWriteSelfTest and HibernateL2CacheReadWriteSelfTest to HibernateL2CacheStrategySelfTest. Merged fix for issue IGNITE-4760 and issue IGNITE-1084 and checked that HibernateL2CacheSelfTest#testNatura

[jira] [Created] (IGNITE-5045) SpringDataExample returns various rows

Sergey Kozlov created IGNITE-5045: - Summary: SpringDataExample returns various rows Key: IGNITE-5045 URL: https://issues.apache.org/jira/browse/IGNITE-5045 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #1847: IGNITE-1439: Added Futures for C++

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1847 IGNITE-1439: Added Futures for C++ You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1439 Alternatively you can re

tcp discovery message exchange

Hi, Igniters! I have a question. What is the purpoise of coordinator sending TcpDiscoveryNodeAddedMessage to every node? We could have just sent TcpDiscoveryNodeAddFinishedMessage instead. -- *Best Regards,* *Kuznetsov Aleksey*

[jira] [Created] (IGNITE-5046) TcpDiscoverySpi.toString() method miss some fields.

Andrew Mashenkov created IGNITE-5046: Summary: TcpDiscoverySpi.toString() method miss some fields. Key: IGNITE-5046 URL: https://issues.apache.org/jira/browse/IGNITE-5046 Project: Ignite

Re: Tickets for work

Nikita, Please find more tickets below: https://issues.apache.org/jira/browse/IGNITE-2190 https://issues.apache.org/jira/browse/IGNITE-4181 https://issues.apache.org/jira/browse/IGNITE-4324 <

Re: need new ticket

Aleksey, Here are more tickets you can start working on: https://issues.apache.org/jira/browse/IGNITE-2190 https://issues.apache.org/jira/browse/IGNITE-4181 https://issues.apache.org/jira/brow

Re: Page Memory behavior with default memory policy

How long will it take to make the memory expandable? Can it be done for 2.0? On Thu, Apr 20, 2017 at 5:25 AM, Sergey Chugunov wrote: > Dmitriy, > > Replied in the ticket. > > Thanks, > Sergey. > > On Wed, Apr 19, 2017 at 10:20 PM, Dmitriy Setrakyan > > wrote: > > > Sergey, > > > > I have respon

[GitHub] ignite pull request #1848: Ignite 5041

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/1848 Ignite 5041 You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-5041 Alternatively you can review and apply these chan

Re: tcp discovery message exchange

As far as I recall, the first message is needed to announce that there is a new node that wishes to join the cluster. The node will receive an order number and will take its place in the cluster ring after the message is processed. The second message is need to finalize the join process: change

Re: Tickets for work

Denis, can you publish these tickets on the Ignite website? On Thu, Apr 20, 2017 at 10:40 AM, Denis Magda wrote: > Nikita, > > Please find more tickets below: > https://issues.apache.org/jira/browse/IGNITE-2190 < > https://issues.apache.org/jira/browse/IGNITE-2190> > https://issues.apache.org/ji

Re: Tickets for work

They can be found if you click on “easy tickets” link under “Pick a ticket” section: https://ignite.apache.org/community/contribute.html#pick-ticket Don’t think we should list them explicitly. — Denis > On Apr 20, 2017, at 10:54 AM, Dmitriy Setrakyan wrote: > > Denis, can you publish these ti

[GitHub] ignite pull request #1836: Ignite 4799

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

[GitHub] ignite pull request #1849: Ignite 4799

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

[jira] [Created] (IGNITE-5047) Apache Ignite Provider for DynaCache

Denis Magda created IGNITE-5047: --- Summary: Apache Ignite Provider for DynaCache Key: IGNITE-5047 URL: https://issues.apache.org/jira/browse/IGNITE-5047 Project: Ignite Issue Type: Task

DynaCache Provider Integration

Igniters, Is there anyone experienced in IBM DynaCache? There is a ticket to provide Apache Ignite and DynaCache integration that is waiting for architectural design and actual implementation: https://issues.apache.org/jira/browse/IGNITE-5047 — Denis

Re: Performance vs correctness: I vote fore the second

Well, I agree that's arguable :) But keeping in mind that the cache is also used for atomics, replicated cache doesn't make sense in any case. Setting default number of backups to 1 for atomics and collections caches should be good enough. -Val On Thu, Apr 20, 2017 at 3:09 PM, Vladimir Ozerov wr

"Apache Ignite University”

I’d also like to propose an enhancement to the community that I believe would be helpful to new and experienced Igniters alike: "Apache Ignite University.” It would be a new section of the Ignite website that features how-to’s in the form of blog posts, videos, even promoting "local" (wherever

Re: "Apache Ignite University”

Great idea! +1 -P On Thu, Apr 20, 2017 at 1:35 PM, Tom Diederich wrote: > I’d also like to propose an enhancement to the community that I believe > would be helpful to new and experienced Igniters alike: "Apache Ignite > University.” > > It would be a new section of the Ignite website that feat

Re: "Apache Ignite University”

Yep, we need it. 2017-04-20 23:48 GMT+03:00 Prachi Garg : > Great idea! +1 > > -P > > On Thu, Apr 20, 2017 at 1:35 PM, Tom Diederich > > wrote: > > > I’d also like to propose an enhancement to the community that I believe > > would be helpful to new and experienced Igniters alike: "Apache Ignite

Please add me to the list

Thanks! :) Tom

Re: "Apache Ignite University”

+1! -- Nikita Ivanov On Thu, Apr 20, 2017 at 1:35 PM, Tom Diederich wrote: > I’d also like to propose an enhancement to the community that I believe > would be helpful to new and experienced Igniters alike: "Apache Ignite > University.” > > It would be a new section of the Ignite website that

Re: Please add me to the list

Tom, What list do you mean? Your emails arrive to Apache Ignite dev list meaning that you’re already subscribed. — Denis > On Apr 20, 2017, at 1:52 PM, Tom Diederich wrote: > > Thanks! :) > Tom > > > > > >

Expiration Policy and Page Memory (Ignite 2.0)

Alex G., Igniters, What’s a scope of expiration policy applicability in Ignite 2.0? Does it work for all the entries in the page memory or only for those that end up in the optional on-heap cache of the page memory? — Denis

Re: "Apache Ignite University”

Sounds good to me. — Denis > On Apr 20, 2017, at 1:35 PM, Tom Diederich wrote: > > I’d also like to propose an enhancement to the community that I believe would > be helpful to new and experienced Igniters alike: "Apache Ignite University.” > > It would be a new section of the Ignite website

Usage of Enums in SQL (Ignite 2.0)

Alexander P., Sergi, Could you give me an example on how to use enums in SQL queries [1] from the user standpoint? It will be ideal if you write a code snippet that demonstrates it. Right after that I’ll add a special section in our SQL Grid documentation. [1] https://issues.apache.org/jira/b

Apache Ignite Nabble is Down

Igniters, Nabble no longer aggregates our discussions. The latest discussions are dated by April 19th. http://apache-ignite-developers.2346864.n4.nabble.com If I try to send a message over its interface then an authentication exception

Re: SQL: Index hints

Sergi, I’ve documented this feature for 2.0. Please confirm that the text below is technically correct: Index hints are useful in scenarios when it's known that one index is more selective for certain queries than another and it's needed to instruct the query optimizer to choose a more efficien

Optimizations on titles and h1

Hi Igniters, I am attaching a patch with keyword optimizations on several page titles and H1 across the website. I would appreciate if any of the committers could merge this to the website. Please let me know if you have any question. Thanks in advance. Best, Mauricio Stekl h1-and-ti

Re: Apache Ignite Nabble is Down

Denis, I think it is working now. Can you check? On Thu, Apr 20, 2017 at 5:48 PM, Denis Magda wrote: > Igniters, > > Nabble no longer aggregates our discussions. The latest discussions are > dated by April 19th. > http://apache-ignite-developers.2346864.n4.nabble.com < > http://apache-ignite-dev

Test

Ignore, testing nuble -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Test-tp16992.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: Apache Ignite Nabble is Down

Yes, recovered, it was a temporary outage on nabble side. On Thu, Apr 20, 2017 at 10:17 PM, Dmitriy Setrakyan wrote: > Denis, I think it is working now. Can you check? > > On Thu, Apr 20, 2017 at 5:48 PM, Denis Magda wrote: > > > Igniters, > > > > Nabble no longer aggregates our discussions. Th

Re: SQL: Index hints

No, it must be USE INDEX without underscore. Also mention that multiple indexes can be listed. http://h2database.com/html/grammar.html#table_expression Sergi 2017-04-21 4:25 GMT+03:00 Denis Magda : > Sergi, I’ve documented this feature for 2.0. Please confirm that the text > below is technical

[jira] [Created] (IGNITE-5048) NPE in WebSessionFilter

Cameron Braid created IGNITE-5048: - Summary: NPE in WebSessionFilter Key: IGNITE-5048 URL: https://issues.apache.org/jira/browse/IGNITE-5048 Project: Ignite Issue Type: Bug Componen

Re: SQL: Index hints

If multiple indexes are listed then H2 will pick only one of them like MySql does, right? Denis On Thursday, April 20, 2017, Sergi Vladykin wrote: > No, it must be USE INDEX without underscore. Also mention that multiple > indexes can be listed. > > http://h2database.com/html/grammar.html#table