Re: documentation suggestions

Denis, Thanks for your comments. The pages I suggested have to do with the "getting started" or "how to's" for Ignite. Burying it inside of other docs will not make sense. That is why I suggested adding them under "Basic Concepts" section, i.e. keep them very visible. D. On Thu, Oct 5, 2017 at

Re: Identifying grid transactions

Hi Igniters, Would it be useful to provide some traceability identifier for messages participating in the partition map exchange? This can be used to filter all logs associated with the exchange. Or now there is some possibility? Sincerely, Dmitriy Pavlov чт, 5 окт. 2017 г. в 2:01, Valentin

[GitHub] ignite pull request #2793: IGNITE-6529: JDBC support 'nullable' column prope...

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

[GitHub] ignite pull request #2805: IGNITE-6556 setSchema() is case sensitive in the ...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2805 IGNITE-6556 setSchema() is case sensitive in the wrong way in Thin JD… …BC driver You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2804: IGNITE-6362: NPE in Log4J2Logger

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/2804 IGNITE-6362: NPE in Log4J2Logger 1. There was an issue inside Log4J2Logger.createConsoleLogger(). null was passed instead of LoggerContext during ad-hoc logger creation via

Re: Adding sqlline tool to Apache Ignite project

Guys, I've created ticket [1] for version 2.4. https://issues.apache.org/jira/browse/IGNITE-6561 2017-08-30 22:21 GMT+03:00 Julian Hyde : > Denis, > > I’m glad you’re thinking of using SQLLine. Under the BSD license, you > don’t need my permission to distribute, but I grant

[jira] [Created] (IGNITE-6560) Web console: New api for memory and persistence configuration

Vasiliy Sisko created IGNITE-6560: - Summary: Web console: New api for memory and persistence configuration Key: IGNITE-6560 URL: https://issues.apache.org/jira/browse/IGNITE-6560 Project: Ignite

[jira] [Created] (IGNITE-6561) Include sqlline in Apache Ignite

Ilya Suntsov created IGNITE-6561: Summary: Include sqlline in Apache Ignite Key: IGNITE-6561 URL: https://issues.apache.org/jira/browse/IGNITE-6561 Project: Ignite Issue Type: Improvement

Re: Adding sqlline tool to Apache Ignite project

Guys, I've created the ticket for 2.4 release: https://issues.apache.org/jira/browse/IGNITE-6561 2017-08-30 22:21 GMT+03:00 Julian Hyde : > Denis, > > I’m glad you’re thinking of using SQLLine. Under the BSD license, you > don’t need my permission to distribute, but I grant

Re: Monitoring of active transactions

Guys, I think we should not limit this functionality to http-rest only. We should add this information to one of the MBeans as the primary information source. Then this should be added as a client command both to http-rest and binary-rest endpoints, so the information is available through

Re: Conflicting cross-version suffixes in: org.scalatest:scalatest, com.twitter:chill, org.apache.spark:spark-unsafe, org.apache.spark:spark-tags

Nikolay I. please chime in as the one who actively works with Ignite Spark integration. — Denis > On Oct 5, 2017, at 5:47 PM, Valentin Kulichenko > wrote: > > +dev list > > Igniters, > > I'm looking at this and it seems to be a bug. We have this dependency in

Re: Spark+Ignite SQL syntax proposal

Nikolay, I don't think we need this, especially with this kind of syntax which is very confusing. Main use case for data frames is SQL, so let's concentrate on it. We should use Ignite's SQL engine capabilities as much as possible. If we see other use cases down the road, we can always support

Re: Issues with cache where class extend base class

Gene, Please share the models of both classes and the SQL query you use. — Denis > On Oct 5, 2017, at 1:53 PM, Gene Fojtik wrote: > > When creating a cached object that extends a base class the extended objects > are not returned upon query. However the objects are

Re: Spark+Ignite SQL syntax proposal

I tend to agree with Val that key-value support seems excessive. My suggestion is to consider Ignite as a SQL database for this specific integration implementing only relevant functionality. — Denis > On Oct 5, 2017, at 5:41 PM, Valentin Kulichenko > wrote: >

Re: Monitoring of active transactions

On Thu, Oct 5, 2017 at 1:24 PM, Alexey Goncharuk wrote: > Guys, > > I think we should not limit this functionality to http-rest only. We should > add this information to one of the MBeans as the primary information > source. Then this should be added as a client

[GitHub] ignite pull request #2808: IGNITE-5224: .NET: PadLeft and PadRight support i...

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/2808 IGNITE-5224: .NET: PadLeft and PadRight support in LINQ You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5224

[GitHub] ignite pull request #2777: IGNITE-6358 JDBC thick: support multiple SQL stat...

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

[GitHub] ignite pull request #2806: IGNITE-6483 Tests for availability of metrics in ...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/2806 IGNITE-6483 Tests for availability of metrics in MX beans. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6483

[jira] [Created] (IGNITE-6566) .NET: IgniteConfiguration.ExecutorConfiguration

Pavel Tupitsyn created IGNITE-6566: -- Summary: .NET: IgniteConfiguration.ExecutorConfiguration Key: IGNITE-6566 URL: https://issues.apache.org/jira/browse/IGNITE-6566 Project: Ignite Issue

[jira] [Created] (IGNITE-6564) Incorrect calculation size and keySize for cluster cache metrics

Ilya Kasnacheev created IGNITE-6564: --- Summary: Incorrect calculation size and keySize for cluster cache metrics Key: IGNITE-6564 URL: https://issues.apache.org/jira/browse/IGNITE-6564 Project:

[GitHub] ignite pull request #2807: IGNITE-6545: Failure during Ignite Service.cancel...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2807 IGNITE-6545: Failure during Ignite Service.cancel() can break normal shutdown process. You can merge this pull request into a Git repository by running: $ git pull

Spark+Ignite SQL syntax proposal

Hello, guys. I’m working on IGNITE-3084 [1] “Spark Data Frames Support in Apache Ignite” and have a proposal to discuss. I want to provide a consistent way to query Ignite key-value caches from Spark SQL engine. To implement it I have to determine java class for the key and value. It required

[jira] [Created] (IGNITE-6562) Dynamic service deployment should use projection if no NodeFilter is set.

Andrew Mashenkov created IGNITE-6562: Summary: Dynamic service deployment should use projection if no NodeFilter is set. Key: IGNITE-6562 URL: https://issues.apache.org/jira/browse/IGNITE-6562

[jira] [Created] (IGNITE-6565) Use long type for size and keySize in cache metrics

Ilya Kasnacheev created IGNITE-6565: --- Summary: Use long type for size and keySize in cache metrics Key: IGNITE-6565 URL: https://issues.apache.org/jira/browse/IGNITE-6565 Project: Ignite

[jira] [Created] (IGNITE-6567) Document JDBC "multipleStatementsAllowed" property

Vladimir Ozerov created IGNITE-6567: --- Summary: Document JDBC "multipleStatementsAllowed" property Key: IGNITE-6567 URL: https://issues.apache.org/jira/browse/IGNITE-6567 Project: Ignite

[jira] [Created] (IGNITE-6563) .NET: ICache.GetLongSize

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

[GitHub] ignite pull request #2805: IGNITE-6556 setSchema() is case sensitive in the ...

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

Re: Enhance persistent store paths: new persistent store folders naming

Hi Denis, Thank you for providing access. Unfortunately I will not be able to start description of this change before 16 Oct. Is it OK? Alternatively can someone from the community pick up this change? All details, algorithm and code references are provided in

Re: Enhance persistent store paths: new persistent store folders naming

Dmitriy, Ok, I’ll take care of the docs. — Denis > On Oct 5, 2017, at 9:41 AM, Dmitry Pavlov wrote: > > Hi Denis, > > Thank you for providing access. > > Unfortunately I will not be able to start description of this change before > 16 Oct. Is it OK? > > Alternatively

Re: Adding sqlline tool to Apache Ignite project

Here is the original ticket [1]. Ilya, closed the one created by you as a duplicate. In addition to the tool’s jar inclusion in Ignite’s binary releases let’s create a shell script to simplify the connectivity phase: name the script as ignitedb.sh for Unix and ignitedb.bat for Windows. the

Re: Enhance persistent store paths: new persistent store folders naming

Thank you! чт, 5 окт. 2017 г., 19:51 Denis Magda : > Dmitriy, > > Ok, I’ll take care of the docs. > > — > Denis > > > On Oct 5, 2017, at 9:41 AM, Dmitry Pavlov wrote: > > > > Hi Denis, > > > > Thank you for providing access. > > > > Unfortunately I will

[GitHub] ignite pull request #2810: IGNITE-6562: Dynamic service deployment should us...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2810 IGNITE-6562: Dynamic service deployment should use projection if no NodeFilter is set. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2809: IGNITE-5852

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

Re: Monitoring of active transactions

On Thu, Oct 5, 2017 at 1:24 PM, Alexey Goncharuk wrote: > Guys, > > I think we should not limit this functionality to http-rest only. We should > add this information to one of the MBeans as the primary information > source. Then this should be added as a client

Re: Identifying grid transactions

>>That's a very useful suggestion. Can it be supported for other APIs as >> well, not only transactions? >> -Val Val, please clarify. What APIs do you mean? --Yakov

[GitHub] ignite pull request #2794: IGNITE-6539: Human readable WAL parser fails if e...

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

[GitHub] ignite pull request #2797: IGNITE-6553: Standalone WAL iterator fails to han...

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

Re: PRIMARY_SYNC+readFromBackup semantics

>>Second of all, it seems that we send a network message from primary node to local backup, which doesn't make much sense to me and looks like unnecessary performance overhead. This does not work. Remember CLOCK mode for atomic updates? We removed that mode. You need globally growing version to

Re: Adding sqlline tool to Apache Ignite project

Would be nice to get it in 2.3. This is critical functionality for our users and 2.4 seems too far to give anyone comfort. On Thu, Oct 5, 2017 at 11:33 AM, Ilya Suntsov wrote: > Guys, > > I've created the ticket for 2.4 release: >

Re: Adding sqlline tool to Apache Ignite project

Dmitriy, Denis We're in progress to add sqlline in upcoming 2.3 On Thu, Oct 5, 2017 at 5:30 PM, Dmitriy Setrakyan wrote: > Would be nice to get it in 2.3. This is critical functionality for our > users and 2.4 seems too far to give anyone comfort. > > On Thu, Oct 5, 2017

Re: Spark+Ignite SQL syntax proposal

Ok. Got it. Will remove key value support from catalog. 6 окт. 2017 г. 6:34 AM пользователь "Denis Magda" написал: > I tend to agree with Val that key-value support seems excessive. My > suggestion is to consider Ignite as a SQL database for this specific > integration

Re: Spark+Ignite SQL syntax proposal

Hello, Valentin. I implemented the ability to make Spark SQL Queries for both: 1. Ignite SQL Table. Internally table described by QueryEntity with meta information about data. 2. Key-Value cache - regular Ignite cache without meta information about stored data. In the second case, we have to

Re: Spark+Ignite SQL syntax proposal

Nikolay, I don't understand. Why do we require to provide key and value types in SQL? What is the issue you're trying to solve with this syntax? -Val On Thu, Oct 5, 2017 at 7:05 AM, Николай Ижиков wrote: > Hello, guys. > > I’m working on IGNITE-3084 [1] “Spark Data

[GitHub] ignite pull request #2812: Modify permissions on $IGNITE_HOME path for OpenS...

GitHub user dwimsey opened a pull request: https://github.com/apache/ignite/pull/2812 Modify permissions on $IGNITE_HOME path for OpenShift Most OpenShift environments run containers using a randomized user id for security purposes. The user is always a member of group 0 however,

[GitHub] ignite pull request #2811: IGNITE-6234 Initialize schemaIds as empty set if ...

GitHub user kristoffSC opened a pull request: https://github.com/apache/ignite/pull/2811 IGNITE-6234 Initialize schemaIds as empty set if schemas field is null Initialize schemaIds as an empty set if schemas field is null and BinaryMetada is deserialized. This behavior is

Re: Conflicting cross-version suffixes in: org.scalatest:scalatest, com.twitter:chill, org.apache.spark:spark-unsafe, org.apache.spark:spark-tags

+dev list Igniters, I'm looking at this and it seems to be a bug. We have this dependency in spark-2.10 module POM: org.json4s json4s-core_2.11 3.5.0 Would replacing it with json4s-core_2.10 be enough to fix? -Val On Thu, Oct 5, 2017 at 5:16 PM, manuelmourato

Issues with cache where class extend base class

When creating a cached object that extends a base class the extended objects are not returned upon query. However the objects are stored, if you iterate through the entire JCache entry. Is this the expected behavior, or do I need to specify a specific annotation. -gene -- Sent from: