Re: Persistent Distributed Store Metrics

On Tue, May 30, 2017 at 2:46 PM, Denis Magda wrote: > I don’t have any extra metrics in mind for now. All I want to say that > presently the Store metrics interface aggregates WAL and checkpointing > metrics and in the future we might add additional Store related metrics >

Re: Persistent Distributed Store Metrics

I don’t have any extra metrics in mind for now. All I want to say that presently the Store metrics interface aggregates WAL and checkpointing metrics and in the future we might add additional Store related metrics there (that has nothing to do with WAL). So, this is why IgniteWalMetrics doesn’t

Re: Persistent Distributed Store Metrics

On Tue, May 30, 2017 at 1:22 PM, Denis Magda wrote: > I’m afraid that in the future we might need to add non WAL related metrics > under this interface. This is why it might make sense to keep the name > generic. > Hm... I am not sure we are going to have any other components

Re: Persistent Distributed Store Metrics

I’m afraid that in the future we might need to add non WAL related metrics under this interface. This is why it might make sense to keep the name generic. — Denis > On May 30, 2017, at 12:29 PM, Dmitriy Setrakyan wrote: > > It looks to me like all global metrics have to

2.1 documentation tasks

Igniters, Here is a list of documentation tasks for 2.1: https://issues.apache.org/jira/browse/IGNITE-5156 Please review and expand it if something is missing. — Denis

[jira] [Created] (IGNITE-5352) Improve ML main page documentation

Denis Magda created IGNITE-5352: --- Summary: Improve ML main page documentation Key: IGNITE-5352 URL: https://issues.apache.org/jira/browse/IGNITE-5352 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-5351) Document K-means clustering algorithm

Denis Magda created IGNITE-5351: --- Summary: Document K-means clustering algorithm Key: IGNITE-5351 URL: https://issues.apache.org/jira/browse/IGNITE-5351 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-5350) Document ordinary least squares (OLS) linear regression

Denis Magda created IGNITE-5350: --- Summary: Document ordinary least squares (OLS) linear regression Key: IGNITE-5350 URL: https://issues.apache.org/jira/browse/IGNITE-5350 Project: Ignite Issue

[jira] [Created] (IGNITE-5349) Document C++ Compute Grid

Denis Magda created IGNITE-5349: --- Summary: Document C++ Compute Grid Key: IGNITE-5349 URL: https://issues.apache.org/jira/browse/IGNITE-5349 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-5348) Document .NET per assembly loading feature

Denis Magda created IGNITE-5348: --- Summary: Document .NET per assembly loading feature Key: IGNITE-5348 URL: https://issues.apache.org/jira/browse/IGNITE-5348 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-5347) Document enums usage in SQL queries

Denis Magda created IGNITE-5347: --- Summary: Document enums usage in SQL queries Key: IGNITE-5347 URL: https://issues.apache.org/jira/browse/IGNITE-5347 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-5345) Update JDBC driver documentation considering the new implementation

Denis Magda created IGNITE-5345: --- Summary: Update JDBC driver documentation considering the new implementation Key: IGNITE-5345 URL: https://issues.apache.org/jira/browse/IGNITE-5345 Project: Ignite

Re: Persistent Distributed Store Metrics

It looks to me like all global metrics have to do with WAL. Why not call them IgniteWalMetrics then? On Tue, May 30, 2017 at 11:58 AM, Denis Magda wrote: > > Also, I see your argument about separating memory from disk metrics, but > I > > think it makes sense to combine them,

[jira] [Created] (IGNITE-5346) Document DDL features: CREATE/DROP, global schema, persistence

Denis Magda created IGNITE-5346: --- Summary: Document DDL features: CREATE/DROP, global schema, persistence Key: IGNITE-5346 URL: https://issues.apache.org/jira/browse/IGNITE-5346 Project: Ignite

Re: Persistent Distributed Store Metrics

> Also, I see your argument about separating memory from disk metrics, but I > think it makes sense to combine them, because it is hard to separate them > from user standpoint. Let's call them IgniteStorageMetrics or something of > the kind. The issue is that we can’t combine all of them because

Re: Persistent Distributed Store Metrics

Several questions: 1. What is "getWalFsyncAverage()"? Is it time? If yes, then it should be consistent with other time metrics, and should be called "getWalFsyncAverageTime()" 2. I see "getPagesOnDisk()", should we also have "getPagesInMemory()"? 3. Also, how about WAL total pages

Re: Default SQL schema name

+1 for public > On May 29, 2017, at 8:31 AM, Alexey Kuznetsov wrote: > > +1 for public > it make sense when copy-pasting SQL queries from ignite to H2 in order to > check how sql works. > > On Mon, May 29, 2017 at 9:21 PM, Pavel Tupitsyn > wrote: >

[GitHub] ignite pull request #2041: Ignite 1.7.11-p1 Release

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/2041 Ignite 1.7.11-p1 Release You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.7.11-p1 Alternatively you can

[jira] [Created] (IGNITE-5344) JDBC Driver: support Statement.closeOnCompletion

Taras Ledkov created IGNITE-5344: Summary: JDBC Driver: support Statement.closeOnCompletion Key: IGNITE-5344 URL: https://issues.apache.org/jira/browse/IGNITE-5344 Project: Ignite Issue

[GitHub] ignite pull request #2038: IGNITE-5337: Renamed C++ example executables for ...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2038 IGNITE-5337: Renamed C++ example executables for Linux You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5337

[GitHub] ignite pull request #2037: IGNITE-5161: Implemented compute example for C++

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2037 IGNITE-5161: Implemented compute example for C++ You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5161

[jira] [Created] (IGNITE-5343) .NET: Interoperate with JVM directly, get rid of C++ layer

Pavel Tupitsyn created IGNITE-5343: -- Summary: .NET: Interoperate with JVM directly, get rid of C++ layer Key: IGNITE-5343 URL: https://issues.apache.org/jira/browse/IGNITE-5343 Project: Ignite

[GitHub] ignite pull request #2033: IGNITE-5338 .NET: TestMultipleAssembliesIndirectD...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2033 --- 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 #2036: Ignite 5075 pds snapshots

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2036 Ignite 5075 pds snapshots PR for tests run, please don't merge. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2028: IGNITE-5333 .NET: Include Apache.Ignite.exe in th...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2028 --- 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 #2035: Ignite 5342 Skip permission check for TASK_EXECUT...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/2035 Ignite 5342 Skip permission check for TASK_EXECUTE for service jobs You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-5342) Skip permission check for TASK_EXECUTE for service jobs

Dmitry Karachentsev created IGNITE-5342: --- Summary: Skip permission check for TASK_EXECUTE for service jobs Key: IGNITE-5342 URL: https://issues.apache.org/jira/browse/IGNITE-5342 Project: Ignite

IGNITE-5087 Enum comparison fails after marshal-unmarshal with BinaryMarshaller

Hello. I done it. Please, review. https://issues.apache.org/jira/browse/IGNITE-5087 - Enum comparison fails after marshal-unmarshal with BinaryMarshaller PR: https://github.com/apache/ignite/pull/2015 ci test:

[jira] [Created] (IGNITE-5341) .NET: DatabaseConfiguration

Pavel Tupitsyn created IGNITE-5341: -- Summary: .NET: DatabaseConfiguration Key: IGNITE-5341 URL: https://issues.apache.org/jira/browse/IGNITE-5341 Project: Ignite Issue Type: Improvement

Re: IgniteCompute async methods do not return ComputeTaskFuture

The fact that closure create task is internal implementation detail which may (and should for performance reasons) change in future. Please provide the use case where use needs anything except for the future itself. On Tue, May 30, 2017 at 2:35 PM, Valentin Kulichenko <

[GitHub] ignite pull request #2034: IGNITE-5335: Fixed reading decimal binary field

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/2034 IGNITE-5335: Fixed reading decimal binary field You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5335

Re: IgniteCompute async methods do not return ComputeTaskFuture

+1 to Yakov. Closure execution also creates a task and I don't see any reason for hiding it. And actually we don't hide it - we fire task/job events, apply the same failover mechanisms, etc. What probably is confusing here is the name of the class. ComputeTaskFuture indeed looks like applied only

[jira] [Created] (IGNITE-5340) AssertionError in index name check

Vladislav Pyatkov created IGNITE-5340: - Summary: AssertionError in index name check Key: IGNITE-5340 URL: https://issues.apache.org/jira/browse/IGNITE-5340 Project: Ignite Issue Type:

Re: Sort nodes in the ring in order to minimize the number of reconnections

Guys, I have just commented in the ticket. I suggest to unschedule IGNITE-4501 from 2.1. Let's return to it at some point. Thanks! --Yakov

Re: IgniteCompute async methods do not return ComputeTaskFuture

Vladimir, I disagree. I understand this is minor issue, but still. Here are the points: 1. TaskSession is supported for all compute methods. Please see - ComputeFailoverExample. Every compute method starts a task. 2. You still return task future, but method return type is a super-interface. 3.

[jira] [Created] (IGNITE-5339) Thin JDBC driver: validate compliance

Vladimir Ozerov created IGNITE-5339: --- Summary: Thin JDBC driver: validate compliance Key: IGNITE-5339 URL: https://issues.apache.org/jira/browse/IGNITE-5339 Project: Ignite Issue Type:

[GitHub] ignite pull request #1972: ignore. PR for test on TC(IGNITE-5227)

Github user mcherkasov closed the pull request at: https://github.com/apache/ignite/pull/1972 --- 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 #2033: IGNITE-5338 .NET: TestMultipleAssembliesIndirectD...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2033 IGNITE-5338 .NET: TestMultipleAssembliesIndirectDependencyMultiLevel fails on TC You can merge this pull request into a Git repository by running: $ git pull

Re: How to return ID of Ignite task to stop this task in the future?

Yakov, q.1 is answered in separate dev-list topic "IgniteCompute async methods do not return ComputeTaskFuture". On Tue, May 30, 2017 at 12:57 PM, Yakov Zhdanov wrote: > Couple of questions to Igniters (cross-posting to dev list). > > 1. Why IgniteCompute does not return

Re: IGNITE-4756

Vadim, I thin you should suggest some format for discussion. Thanks! -- Yakov Zhdanov, Director R *GridGain Systems* www.gridgain.com 2017-05-30 13:09 GMT+03:00 Вадим Опольский : > Hello guys! > > I want to resolve isuue - https://issues.apache.org/ >

[jira] [Created] (IGNITE-5338) .NET: TestMultipleAssembliesIndirectDependencyMultiLevel fails on TC

Pavel Tupitsyn created IGNITE-5338: -- Summary: .NET: TestMultipleAssembliesIndirectDependencyMultiLevel fails on TC Key: IGNITE-5338 URL: https://issues.apache.org/jira/browse/IGNITE-5338 Project:

IGNITE-4756

Hello guys! I want to resolve isuue - https://issues.apache.org/jira/browse/IGNITE-4756 But cant find information about where to create log message in correct format. Help please. Vadim Opolski

[jira] [Created] (IGNITE-5337) C++ linux examples: names of executable files should be the same type

Irina Zaporozhtseva created IGNITE-5337: --- Summary: C++ linux examples: names of executable files should be the same type Key: IGNITE-5337 URL: https://issues.apache.org/jira/browse/IGNITE-5337

Re: Cassandra and Ignite C++ Issue

Thanks. Best Regards, Igor On Tue, May 30, 2017 at 11:35 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Igor, > > There is another SO question about this, I already responded: > https://stackoverflow.com/questions/44254079/ignite- > with-cassandra-integration > > -Val > > On

Re: DiscoverySpi#setDataExchange returns concrete implementation

yes --Yakov 2017-05-29 17:30 GMT+03:00 Николай Ижиков : > Thanks Yakov. > > I moved IGNITE-5321 to resolved state. > Is that right? > > 2017-05-29 17:24 GMT+03:00 Yakov Zhdanov : > > > Merged. Thanks for contribution, Nick. Please also see my edits.

Re: Cassandra and Ignite C++ Issue

Igor, There is another SO question about this, I already responded: https://stackoverflow.com/questions/44254079/ignite-with-cassandra-integration -Val On Tue, May 30, 2017 at 10:15 AM, Igor Sapego wrote: > User's answer: > I have changed my POJO to BLOB. > > Current

Re: IgniteCompute async methods do not return ComputeTaskFuture

Valya, This future contains task session. We intentionally changed return type to plain IgniteFuture for closure methods, as there is no notion of "session" and "task" for them. ComputeTaskFuture now returned only from task-related methods ("execute"). Unless I am missing something, this approach

Re: Cassandra and Ignite C++ Issue

User's answer: I have changed my POJO to BLOB. Current persistence.xml file look like now it's produce an error like "Caused by: com.datastax.driver.core.exceptions.CodecNotFoundException: Codec not found for requested operation: [varchar <-> java.nio.HeapByteBuffer] " Best Regards,

IgniteCompute async methods do not return ComputeTaskFuture

Folks, I noticed that the new async API for IgniteCompute returns IgniteFuture, while previously we used to have its extension - ComputeTaskFuture, which contains useful information about the executed task session. Should this be fixed? -Val

[GitHub] ignite pull request #2027: IGNITE-5334

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/2027 --- 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-5336) Add documentation for JDBC thick driver BLOB support

Vladimir Ozerov created IGNITE-5336: --- Summary: Add documentation for JDBC thick driver BLOB support Key: IGNITE-5336 URL: https://issues.apache.org/jira/browse/IGNITE-5336 Project: Ignite