[GitHub] ignite pull request #1363: ignite-1.8.2

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

Re: NullPointerException on ScanQuery

Hi all. Is there any comment on this? -- Alper Tekinalp Software Developer Evam Streaming Analytics Atatürk Mah. Turgut Özal Bulv. Gardenya 5 Plaza K:6 Ataşehir 34758 İSTANBUL Tel: +90 216 455 01 53 Fax: +90 216 455 01 54 www.evam.com.tr

Cache Metrics

Hi all. I have the following code: IgniteConfiguration igniteConfiguration = new IgniteConfiguration(); igniteConfiguration.setGridName("alper"); Ignite start = Ignition.start(igniteConfiguration); CacheConfiguration configuration = new CacheConfiguration();

Re: Cache Metrics

Hi, Alper! Could you try to set configuration.setStatisticsEnabled(true) and try once again? On Tue, Dec 20, 2016 at 3:41 PM, Alper Tekinalp wrote: > Hi all. > > I have the following code: > IgniteConfiguration igniteConfiguration = new > IgniteConfiguration(); > igniteConfigur

Make async API great again

Igniters, We have complaints about design of our async API, and upcoming Ignite 2.0 release is a good candidate to fix it. Problems: 1) API is verbose and error prone: Ignite asyncCache = cache.withAsync(); asyncCache.get(key); IgniteFuture fut = asyncCache.future(); 2) Hard to reason which me

[GitHub] ignite pull request #1364: IGNITE-4372: Set up code coverage reports

GitHub user ksuksu1601 opened a pull request: https://github.com/apache/ignite/pull/1364 IGNITE-4372: Set up code coverage reports You can merge this pull request into a Git repository by running: $ git pull https://github.com/ksuksu1601/ignite ignite-4372 Alternatively you c

Re: Communication from JDBC/ODBC drivers

I see what you are suggesting and will remove this feature from the driver if there are no objections. (Anyone?) Still, for clarity and your better understanding I'd like to again point out that there's no thread context switching or any Ignite imposed overhead by default as even ignite compute ia

Re: Batch DML queries design discussion

Auto flush freq is already there, I just forgot to mention it in the comments. Will add the rest today. — Alex 19 дек. 2016 г. 10:29 PM пользователь "Denis Magda" написал: > Alexander, > > A couple of comments in regards to the streaming mode. > > I would rename rename the existed property to “i

Re: Communication from JDBC/ODBC drivers

On Tue, Dec 20, 2016 at 1:23 AM, Alexander Paschenko < alexander.a.pasche...@gmail.com> wrote: > I see what you are suggesting and will remove this feature from the driver > if there are no objections. (Anyone?) > Still, for clarity and your better understanding I'd like to again point > out that

Re: Make async API great again

Huge +1 on this. Current API is very confusing. On Tue, Dec 20, 2016 at 11:56 AM, Vladimir Ozerov wrote: > Igniters, > > We have complaints about design of our async API, and upcoming Ignite 2.0 > release is a good candidate to fix it. > > Problems: > > 1) API is verbose and error prone: > > Ign

Re: NullPointerException on ScanQuery

Hi, As I wrote already I don't see any race for stable topology. Problems are possible on unstable topology. You can try wait for topology version will be the same on all nodes in cluster and avoid this race. Unfortunately I can't see your code except of example that has some drawbacks mentioned

[GitHub] ignite pull request #1365: Ignite 3292

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

[GitHub] ignite pull request #1366: Ignite 2466

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

Re: Make async API great again

+1 在 2016/12/20 18:05, Pavel Tupitsyn 写道: Huge +1 on this. Current API is very confusing. On Tue, Dec 20, 2016 at 11:56 AM, Vladimir Ozerov wrote: Igniters, We have complaints about design of our async API, and upcoming Ignite 2.0 release is a good candidate to fix it. Problems: 1) API i

[GitHub] ignite pull request #1367: IGNITE-4248: Slf4jLogger ignores IGNITE_QUIET sys...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1367 IGNITE-4248: Slf4jLogger ignores IGNITE_QUIET system property Fixed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite i

[jira] [Created] (IGNITE-4464) JclLogger ignores IGNITE_QUIET system property

Andrew Mashenkov created IGNITE-4464: Summary: JclLogger ignores IGNITE_QUIET system property Key: IGNITE-4464 URL: https://issues.apache.org/jira/browse/IGNITE-4464 Project: Ignite Issue

Hello everyone

Hello everyone. I want to help community with development of Apache Ignite. I was wondering if you could give me some advice. With best regards, Vyacheslav Daradur

[GitHub] ignite pull request #1343: IGNITE-1443: Implemented ContinuousQuery for C++.

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

[GitHub] ignite pull request #1368: IGNITE-4462: Remove grid name from HadoopIgfsEndp...

GitHub user taras-ledkov opened a pull request: https://github.com/apache/ignite/pull/1368 IGNITE-4462: Remove grid name from HadoopIgfsEndpoint You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4462

Re: Make async API great again

The impact of this change seems quite significant. Also, some of the issues, like starvation, will not be fixed with introduction of the new API, as far as I can tell. I would be against removing the current async support from the API in one motion. I think we can deprecate it right now, in 2.0, a

Re: Make async API great again

I don't think that increased method number in the API is an issue. Modern IDEs have sophisticated auto-complete features that make it easy to find the right one. As an API user, I would prefer sync and async methods side by side in the same interface: Use types 'cache.get(' and the IDE would show

Re: Make async API great again

On Tue, Dec 20, 2016 at 9:13 AM, Pavel Tupitsyn wrote: > I don't think that increased method number in the API is an issue. > Modern IDEs have sophisticated auto-complete features that make it easy to > find the right one. > It is not an issue of IDE support. It is an issue of API complexity and

Re: Communication from JDBC/ODBC drivers

OK, will remove redundant query tasks creation for the case of DML statements - they at least incur some GC overhead even if not context switching. - Alex 2016-12-20 12:49 GMT+03:00 Dmitriy Setrakyan : > On Tue, Dec 20, 2016 at 1:23 AM, Alexander Paschenko < > alexander.a.pasche...@gmail.com> wro

Re: Make async API great again

+1 For removing withAsync. It is a broken design. Sergi 2016-12-20 20:38 GMT+03:00 Dmitriy Setrakyan : > On Tue, Dec 20, 2016 at 9:13 AM, Pavel Tupitsyn > wrote: > > > I don't think that increased method number in the API is an issue. > > Modern IDEs have sophisticated auto-complete features th

Re: Make async API great again

On Tue, Dec 20, 2016 at 10:28 AM, Sergi Vladykin wrote: > +1 For removing withAsync. It is a broken design. > Sergi, do you also want to add all the async methods to the main API or do you have some other design in mind?

Fwd: Cache Metrics

Cross sending this to dev. Igniters, why does the metrics stuff have to be so confusing? Looks like if "statisticsEnabled" is false, then metrics return all 0s. Can we at least have a warning in the log stating that the metrics are disabled, and explaining how to enable them? D. -- Forwa

Re: Make async API great again

Me personal preference is to have a separate interface with all the supported async methods. Basically in 2.0 we can have the same withAsync() method but it will return this new interface. Sergi 2016-12-20 21:31 GMT+03:00 Dmitriy Setrakyan : > On Tue, Dec 20, 2016 at 10:28 AM, Sergi Vladykin >

Re: Make async API great again

We already discussed this several months ago in other thread. "Async" methods is the most simple and straight API possible. .NET world goes this way all over their frameworks and nobody died. Hazelcast also goes this way. Java goes this way (see CompletableFuture). This is common and well-known pr

Re: NullPointerException on ScanQuery

Hi Andrey, Do you have an idea what is causing the NPE in the first place? What is null? I didn't quite get it from the thread. -Val On Tue, Dec 20, 2016 at 2:14 AM, Andrey Gura wrote: > Hi, > > As I wrote already I don't see any race for stable topology. Problems > are possible on unstable to

Re: Make async API great again

How difficult is this change? Does not look like it can be done overnight. On Tue, Dec 20, 2016 at 10:46 AM, Vladimir Ozerov wrote: > We already discussed this several months ago in other thread. > > "Async" methods is the most simple and straight API possible. .NET world > goes this way all ove

Diagram for RDBMS Schema Import with Web Console

Igniters, Alexey Kuznetsov has contributed the documentation which describes how to import a database schema converting it into Ignite’s configuration and project files https://apacheignite-mix.readme.io/v1.8/docs/web-console The last

Re: Hello

Alexander, CC-ing the dev list to keep everyone in track. I hope the case you’re talking about can be already implemented by the usage of RendezvousAffinityFunction.setAffinityBackupFilter(…) method [1]. This method gives you a way to control a locality of your primary and backup nodes. Depend

Re: Communication from JDBC/ODBC drivers

Guys, Doesn’t it make sense to wait for 2.0 release where we’re free to break the compatibility by removing deprecated or bad designed APIs? There is a chance that this JDBC’s “nodeId” parameter is being used by someone. — Denis > On Dec 20, 2016, at 10:18 AM, Alexander Paschenko > wrote: >

Re: Make async API great again

Async API rework is mechanical addition of ~100 methods through copy-paste. Should not take more than a day to implement and more than another day to rework tests. On Tue, Dec 20, 2016 at 10:00 PM, Dmitriy Setrakyan wrote: > How difficult is this change? Does not look like it can be done overnig

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

Summarized the discussion updating the ticket https://issues.apache.org/jira/browse/IGNITE-4212# — Denis > On Dec 19, 2016, at 12:26 PM, Dmitriy Setrakyan wrote: > > Sergey, > > I am not sure I like "extras". I am voting for "benchmarks" fo

Re: Hello everyone

Hi Vyacheslav, Welcome to the Ignite community! Subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on

Re: Capacity Planning - Calculating Memory Usage

What is the relationship of apacheignite.gridgain.org to the open source Apache Ignite project? Thanks! On Tue, Dec 13, 2016 at 2:37 AM, Alexandr Kuramshin wrote: > Hello, Igniters, > > I'd like to represent updated article [1] about the subject. > > And I'll very appreciate your comments and qu

Ignite Shutdown Hook

Hi, I am starting Ignite as standalone program embedded in my java application via Spring configuration. It works great however my application stucks and never finishes. I have added some shutdown hooks but they are never called. I think this is because Ignite is running in main thread and stoppin

Re: Ignite Shutdown Hook

+ user list On Tue, Dec 20, 2016 at 12:30 PM, hemanta wrote: > Hi, > > I am starting Ignite as standalone program embedded in my java application > via Spring configuration. It works great however my application stucks and > never finishes. I have added some shutdown hooks but they are never cal

Re: Capacity Planning - Calculating Memory Usage

This is the documentation domain that has been left historically. In general, Ignite was contributed to Apache by GridGain a couple of years ago and now GridGain provides additional enterprise level features on top of Ignite. The valid link to the doc is: https://apacheignite.readme.io/docs/capa

[GitHub] ignite pull request #1369: IGNITE-4439 - Attribute based node filter

GitHub user vkulichenko opened a pull request: https://github.com/apache/ignite/pull/1369 IGNITE-4439 - Attribute based node filter You can merge this pull request into a Git repository by running: $ git pull https://github.com/vkulichenko/ignite ignite-4439 Alternatively you

Node attribute filter

Guys, I created a simple implementation of IgnitePredicate based on user attributes. This is the most commonly used approach for node filters, but currently users are forced to create their own implementations each time. Would be useful to have it out of the box. Can someone take a look at the im

Re: Ignite Shutdown Hook

Hi, I'm not sure I understand the problem... Where is the application stuck? Did you look at thread dump? -Val On Tue, Dec 20, 2016 at 12:30 PM, hemanta wrote: > Hi, > > I am starting Ignite as standalone program embedded in my java application > via Spring configuration. It works great howeve

Re: Make async API great again

Would be nice if someone would prototype a new cache API and post the generated javadoc here. I think we all will benefit from reviewing it. On Tue, Dec 20, 2016 at 12:17 PM, Vladimir Ozerov wrote: > Async API rework is mechanical addition of ~100 methods through copy-paste. > Should not take mo

Re: Diagram for RDBMS Schema Import with Web Console

Thanks, Denis! The diagram you created looks nice. On Tue, Dec 20, 2016 at 11:53 AM, Denis Magda wrote: > Igniters, > > Alexey Kuznetsov has contributed the documentation which describes how to > import a database schema converting it into Ignite’s configuration and > project files > https://apa

Re: Diagram for RDBMS Schema Import with Web Console

Denis, I attached slightly corrected diagram: https://issues.apache.org/jira/secure/attachment/12844178/SchemaImport-2.png On Wed, Dec 21, 2016 at 8:35 AM, Dmitriy Setrakyan wrote: > Thanks, Denis! The diagram you created looks nice. > > On Tue, Dec 20, 2016 at 11:53 AM, Denis Magda wrote: > >

[jira] [Created] (IGNITE-4465) Read-through is not properly working with multiple gets executed in parallel

Valentin Kulichenko created IGNITE-4465: --- Summary: Read-through is not properly working with multiple gets executed in parallel Key: IGNITE-4465 URL: https://issues.apache.org/jira/browse/IGNITE-4465

Re: Concurrent read-through

Guys, I'd like to resurrect this discussion as it seems to me that I found more serious issue here. Here is the ticket: https://issues.apache.org/jira/browse/IGNITE-4465. Can someone take a look at it? Basically, it looks like under some circumstances we can get a cache miss after the value was a

[jira] [Created] (IGNITE-4466) Web console - Admin panel: show different message for 'Grant\Revoke admin' actions

Pavel Konstantinov created IGNITE-4466: -- Summary: Web console - Admin panel: show different message for 'Grant\Revoke admin' actions Key: IGNITE-4466 URL: https://issues.apache.org/jira/browse/IGNITE-4466

Re: NullPointerException on ScanQuery

Hi Val. Do you have an idea what is causing the NPE in the first place? As Andrey says the exception is caused because of different topology versions cluster nodes. > What is null? > Node is null in the following code in org.apache.ignite.internal.processors.cache.query.ScanQueryFallbackClosa

[jira] [Created] (IGNITE-4467) Web Console: Refactor CSS

Alexey Kuznetsov created IGNITE-4467: Summary: Web Console: Refactor CSS Key: IGNITE-4467 URL: https://issues.apache.org/jira/browse/IGNITE-4467 Project: Ignite Issue Type: Task