Re: Storing deserialized value when indexing is enabled

Looks like a known issue to me, I've linked related tickets in Jira: https://issues.apache.org/jira/browse/IGNITE-2417 https://issues.apache.org/jira/browse/IGNITE-3347 On Thu, Nov 24, 2016 at 12:13 AM, Denis Magda wrote: > Val, > > Yeah, the code is like jungles in some

Re: Blogging about new .NET features

Denis, sure, I think I'll start with "What's new in Ignite.NET 1.8" and write in more detail about big features later. On Wed, Nov 23, 2016 at 9:34 PM, Denis Magda wrote: > Pavel, > > Do you mind blogging about ASP.NET session state [1] and Entity Framework > 2nd level

[GitHub] ignite pull request #1274: IGNITE-4205 CassandraCacheStore should start Igni...

GitHub user irudyak opened a pull request: https://github.com/apache/ignite/pull/1274 IGNITE-4205 CassandraCacheStore should start IgniteThread threads in loadCache() method You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1273: IGNITE-4282: Javadoc broken.

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/1273 IGNITE-4282: Javadoc broken. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite ignite-4282 Alternatively you can review and

Re: [DISCUSS] PMC Chair rotation time

Cos, I will start the vote soon. A bit over occupied with travel and holidays at this moment. On Mon, Nov 21, 2016 at 12:33 PM, Konstantin Boudnik wrote: > Ok, > > This was a great discussion, thanks for the deep insight, Roman! > > looks like this thread has stewed for a while

Re: In-Memory SQL Grid

I like SQL Grid, seems consistent. I think that DML support is huge for the project! D. On Wed, Nov 23, 2016 at 12:08 PM, Denis Magda wrote: > Community, > > Frankly speaking, Ignite’s SQL support goes far beyond the notion of Data > Grid starting from Apache Ignite 1.8. >

Re: Storing deserialized value when indexing is enabled

Val, Yeah, the code is like jungles in some places. Proposed a possible fix inside of the ticket. — Denis > On Nov 23, 2016, at 1:01 PM, Valentin Kulichenko > wrote: > > Denis, > > CacheObjectBinaryProcessorImpl calls super and preserves the value of >

FOSDEM 2017 HPC, Bigdata and Data Science DevRoom CFP is closing soon

Hi! apologies for the extra wide distribution (this exhausts my once a year ASF mail-to-all-bigdata-projects quota ;-)) but I wanted to suggest that all of you should consider submitting talks to FOSDEM 2017 HPC, Bigdata and Data Science DevRoom: https://hpc-bigdata-fosdem17.github.io/ It

Re: Start contributing

Hi Maks, Welcome to the Ignite community! You should get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be found here:

Re: Hello

Here are some ticket you may want to start with https://ignite.apache.org/community/contribute.html#pick-ticket — Denis > On Nov 23, 2016, at 5:33 AM, Dmitriy Setrakyan wrote: > > Hi Alex, > > Welcome to

[jira] [Created] (IGNITE-4293) Deserialized value is cached if queries are enabled

Valentin Kulichenko created IGNITE-4293: --- Summary: Deserialized value is cached if queries are enabled Key: IGNITE-4293 URL: https://issues.apache.org/jira/browse/IGNITE-4293 Project: Ignite

Re: Storing deserialized value when indexing is enabled

Denis, CacheObjectBinaryProcessorImpl calls super and preserves the value of storeVal flag. It seems to me that it's then used in BinaryObjectImpl.deserializeValue() causing the deserialized value to be saved in memory. This doubles memory consumption in this scenario. I created a ticket:

Apache Ignite Contribution: Kubernetes, Streaming, Data Structures and More

Guys, If someone of you locates in the U.S. and doesn’t know how to spend upcoming holidays effectively I would remind that Ignite might make this days more colorful and memorable. What you need to do is to pick up a ticket of interest and contribute it to the project.

Re: [jira] [Created] (IGNITE-4292) SQL: Except returns incorrect results

Thank you, Val! I will follow your suggestion. Rohit On Wed, Nov 23, 2016 at 10:22 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Rohit, > > If you unsubscribe, your messages will not be redirected to the list what > you post on Nabble, which means that majority of

Storing deserialized value when indexing is enabled

Folks, It looks like we cache the deserialized value in case indexing is enabled and a read operation happens on server side (e.g. affinity closure does get() on primary node). This must be caused by this piece of code in IgniteCacheObjectProcessorImpl: boolean storeVal =

In-Memory SQL Grid

Community, Frankly speaking, Ignite’s SQL support goes far beyond the notion of Data Grid starting from Apache Ignite 1.8. SQL in Ignite is no longer about distributed ANSI-99 SELECT queries only. It will be about the ability to connect to an Ignite Cluster not only from Java, .NET and C++

SparkRDD with Ignite

Have been extensively trying to integrate spark rdd's with ignite. We have spark version 1.6.1 with apache-ignite-1.6.0-src. Tried out the example in "https://apacheignite-fs.readme.io/docs/testing-integration-with-spark-shell​; and it is working fine. However, all efforts w.r.t connecting to

Blogging about new .NET features

Pavel, Do you mind blogging about ASP.NET session state [1] and Entity Framework 2nd level cache [2] support after 1.8 release goes public? Also I would remind everyone in the community that it’s always welcomed to share your experience or Ignite related news over blog posts. We track all the

Re: [jira] [Created] (IGNITE-4292) SQL: Except returns incorrect results

Hi Rohit, If you unsubscribe, your messages will not be redirected to the list what you post on Nabble, which means that majority of community members will not read them. I recommend you to just filter out emails you don't need. -Val On Wed, Nov 23, 2016 at 10:12 AM, Pavel Tupitsyn

Re: [jira] [Created] (IGNITE-4292) SQL: Except returns incorrect results

Thank you, Pavel! Can you please unsubscribe me from the emails? Thanks, Rohit On Wed, Nov 23, 2016 at 9:52 AM, Pavel Tupitsyn wrote: > Hi, yes, you can use online mail archives: > http://apache-ignite-developers.2346864.n4.nabble.com/ > > On Wed, Nov 23, 2016 at 8:48

Re: [jira] [Created] (IGNITE-4292) SQL: Except returns incorrect results

Hi, yes, you can use online mail archives: http://apache-ignite-developers.2346864.n4.nabble.com/ On Wed, Nov 23, 2016 at 8:48 PM, Rohit Gupta wrote: > Hello, > > I am sorry to bother you. I am wondering if I can follow the discussion > online without getting emails.

Re: [jira] [Created] (IGNITE-4292) SQL: Except returns incorrect results

Hello, I am sorry to bother you. I am wondering if I can follow the discussion online without getting emails. Please let me know. Thank you! Sincerely, Rohit On Wed, Nov 23, 2016 at 9:34 AM, Pavel Tupitsyn (JIRA) wrote: > Pavel Tupitsyn created IGNITE-4292: >

[jira] [Created] (IGNITE-4292) SQL: Except returns incorrect results

Pavel Tupitsyn created IGNITE-4292: -- Summary: SQL: Except returns incorrect results Key: IGNITE-4292 URL: https://issues.apache.org/jira/browse/IGNITE-4292 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-4291) SQL: Multi-from join returns no results

Pavel Tupitsyn created IGNITE-4291: -- Summary: SQL: Multi-from join returns no results Key: IGNITE-4291 URL: https://issues.apache.org/jira/browse/IGNITE-4291 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-4290) SQL: Three-way join returns no results

Pavel Tupitsyn created IGNITE-4290: -- Summary: SQL: Three-way join returns no results Key: IGNITE-4290 URL: https://issues.apache.org/jira/browse/IGNITE-4290 Project: Ignite Issue Type: Bug

Re: Apache Ignite 1.8 Release

Denis, I've raised PRs and Vladimir has merged them into ignite-1.8. But now we have some failing ODBC tests in the branch. I'm currently working on them. There is a ticket for that which you can track [1]. I'll add all my findings there. [1] https://issues.apache.org/jira/browse/IGNITE-4288

Re: Apache Ignite 1.8 Release

Alexander, Awesome news, thanks for making this happen! Igor S., have you merged all ODBC-DML-PHP/PDO related changes? Can I start testing that PHP-PDO guidance [1] is correct? [1] https://apacheignite.readme.io/docs/pdo-interoperability

[GitHub] ignite pull request #1272: IGNITE-4288: Fix for 32-bit verions.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1272 IGNITE-4288: Fix for 32-bit verions. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-4288 Alternatively you can review

[jira] [Created] (IGNITE-4288) ODBC: Fix ODBC and DML interoperability.

Igor Sapego created IGNITE-4288: --- Summary: ODBC: Fix ODBC and DML interoperability. Key: IGNITE-4288 URL: https://issues.apache.org/jira/browse/IGNITE-4288 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #1271: IGNITE-4157 Use discovery custom events instead o...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1271 IGNITE-4157 Use discovery custom events instead of marshaller and system cache First version of feature's implementation. You can merge this pull request into a Git repository by

[GitHub] ignite pull request #1270: IGNITE-4063 BinaryType.fieldNames() should return...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1270 IGNITE-4063 BinaryType.fieldNames() should return names in consistent order You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-4287) DML: DELETE statement failed: Invalid number of query parameters. Cannot find 2 parameter.

Sergey Kozlov created IGNITE-4287: - Summary: DML: DELETE statement failed: Invalid number of query parameters. Cannot find 2 parameter. Key: IGNITE-4287 URL: https://issues.apache.org/jira/browse/IGNITE-4287

[GitHub] ignite pull request #1269: IGNITE-3910: Implemented SQLDescribeParam.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1269 IGNITE-3910: Implemented SQLDescribeParam. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3910 Alternatively

Re: Apache Ignite 1.8 Release

Regarding failing tests mentioned in IGNITE-4280 (IgniteBinaryCacheQueryTestSuite related ones): reason found (incorrect handling of old configurations where QueryEntities don't have keyFields field), working on the patch. - Alex 2016-11-23 16:01 GMT+03:00 Sergey Kozlov : >

Re: Hello

Hi Alex, Welcome to the Ignite community! Once you are familiar with the contribution process, please see if there is a specific Jira ticket you would like work on. We will help you get started. D. On Wed, Nov 23, 2016 at 2:24 AM, Vladislav Pyatkov wrote: > Please read

[GitHub] ignite pull request #1268: IGNITE-3640 IGFS: Local secondary: Investigate wh...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1268 IGNITE-3640 IGFS: Local secondary: Investigate whether we need BufferedInputStream for open operation. You can merge this pull request into a Git repository by running: $ git

Re: Start Contributing

Hi Nikita, Welcome to the Ignite community! Once you are familiar with the contribution process, please see if there is a specific Jira ticket you would like to get started with. D. On Wed, Nov 23, 2016 at 1:55 AM, Alexey Kuznetsov wrote: > Hi, Nikita! > > Please read

Start contributing

Hello -- Best regards, Maks Kozlov

Re: Apache Ignite 1.8 Release

Hi I've started the testing of the key feature introducing for 1.8: DML On Wed, Nov 23, 2016 at 1:01 PM, Vladimir Ozerov wrote: > Hi Alex, > That is very good news! I created branch *ignite-1.8* and merged your > changes there. Thank you for contribution! > > Igniters, >

[GitHub] ignite pull request #1264: IGNITE-4281

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1264 --- 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 #1266: IGNITE-4271

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1266 --- 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-4286) Hadoop: use plain property names.

Vladimir Ozerov created IGNITE-4286: --- Summary: Hadoop: use plain property names. Key: IGNITE-4286 URL: https://issues.apache.org/jira/browse/IGNITE-4286 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-4284) Failed second client node join with continuous query and peer class loading enabled

Dmitry Karachentsev created IGNITE-4284: --- Summary: Failed second client node join with continuous query and peer class loading enabled Key: IGNITE-4284 URL: https://issues.apache.org/jira/browse/IGNITE-4284

[GitHub] ignite pull request #1267: IGNITE-4284 - Test

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1267 IGNITE-4284 - Test You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4284 Alternatively you can review and

[GitHub] ignite pull request #1266: IGNITE-4271

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

[GitHub] ignite pull request #1265: IGNITE-4016: IGNITE-4016: ODBC example now uses D...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1265 IGNITE-4016: IGNITE-4016: ODBC example now uses DML. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4016

[GitHub] ignite pull request #1264: IGNITE-4281

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

[jira] [Created] (IGNITE-4282) Javadoc broken

Ilya Suntsov created IGNITE-4282: Summary: Javadoc broken Key: IGNITE-4282 URL: https://issues.apache.org/jira/browse/IGNITE-4282 Project: Ignite Issue Type: Bug Components:

[jira] [Created] (IGNITE-4281) Hadoop: decouple mapper and reducer maps.

Vladimir Ozerov created IGNITE-4281: --- Summary: Hadoop: decouple mapper and reducer maps. Key: IGNITE-4281 URL: https://issues.apache.org/jira/browse/IGNITE-4281 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4280) Fix failing tests in IgniteBinaryCacheQueryTestSuite

Alexander Paschenko created IGNITE-4280: --- Summary: Fix failing tests in IgniteBinaryCacheQueryTestSuite Key: IGNITE-4280 URL: https://issues.apache.org/jira/browse/IGNITE-4280 Project: Ignite

[jira] [Created] (IGNITE-4279) Make DML related JDBC driver tests pass within suite

Alexander Paschenko created IGNITE-4279: --- Summary: Make DML related JDBC driver tests pass within suite Key: IGNITE-4279 URL: https://issues.apache.org/jira/browse/IGNITE-4279 Project: Ignite

Re: Hello

Please read https://ignite.apache.org/community/contribute.html#contribute Looking forward for your contributions! On Wed, Nov 23, 2016 at 1:15 PM, Александр Меньшиков wrote: > I want to contribute. > > 2016-11-23 13:04 GMT+03:00 Vladislav Pyatkov :

Re: Hello

I want to contribute. 2016-11-23 13:04 GMT+03:00 Vladislav Pyatkov : > Hi Alex, > > This is Apache Ignite development community. > Are you want to contribute to Ignite or you are have any suggestion? > > On Wed, Nov 23, 2016 at 12:41 PM, Александр Меньшиков < >

Re: Hello

Hi Alex, This is Apache Ignite development community. Are you want to contribute to Ignite or you are have any suggestion? On Wed, Nov 23, 2016 at 12:41 PM, Александр Меньшиков wrote: > Hello >

Re: Apache Ignite 1.8 Release

Hi Alex, That is very good news! I created branch *ignite-1.8* and merged your changes there. Thank you for contribution! Igniters, Let's finalize all remaining tickets in the scope of *ignite-1.8 *branch. Hopefully we will be ready for vote in several days. Vladimir. On Wed, Nov 23, 2016 at

Re: Start Contributing

Hi, Nikita! Please read https://ignite.apache.org/community/contribute.html#contribute Looking forward for your contributions! On Wed, Nov 23, 2016 at 3:59 PM, Никита Амельчев wrote: > Hello everybody! > > I want to contribute this project. > > -- > Best wishes, >

[jira] [Created] (IGNITE-4278) Hadoop: investigate why small array copying is slow on PPC.

Vladimir Ozerov created IGNITE-4278: --- Summary: Hadoop: investigate why small array copying is slow on PPC. Key: IGNITE-4278 URL: https://issues.apache.org/jira/browse/IGNITE-4278 Project: Ignite

[jira] [Created] (IGNITE-4277) Hadoop: support raw comparator.

Vladimir Ozerov created IGNITE-4277: --- Summary: Hadoop: support raw comparator. Key: IGNITE-4277 URL: https://issues.apache.org/jira/browse/IGNITE-4277 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-4276) Hadoop: control shuffle jobs "sleep" backpressure with property.

Vladimir Ozerov created IGNITE-4276: --- Summary: Hadoop: control shuffle jobs "sleep" backpressure with property. Key: IGNITE-4276 URL: https://issues.apache.org/jira/browse/IGNITE-4276 Project:

[jira] [Created] (IGNITE-4274) Hadoop: control shuffle message buffer size through property.

Vladimir Ozerov created IGNITE-4274: --- Summary: Hadoop: control shuffle message buffer size through property. Key: IGNITE-4274 URL: https://issues.apache.org/jira/browse/IGNITE-4274 Project: Ignite

[jira] [Created] (IGNITE-4275) Hadoop: create separate property to avoid sorting of mapper output.

Vladimir Ozerov created IGNITE-4275: --- Summary: Hadoop: create separate property to avoid sorting of mapper output. Key: IGNITE-4275 URL: https://issues.apache.org/jira/browse/IGNITE-4275 Project:

[jira] [Created] (IGNITE-4273) Hadoop: implement head-based data structures.

Vladimir Ozerov created IGNITE-4273: --- Summary: Hadoop: implement head-based data structures. Key: IGNITE-4273 URL: https://issues.apache.org/jira/browse/IGNITE-4273 Project: Ignite Issue

[jira] [Created] (IGNITE-4272) Hadoop: shuffle messages must always be processed asynchronously wtr to shuffle job or mapper.

Vladimir Ozerov created IGNITE-4272: --- Summary: Hadoop: shuffle messages must always be processed asynchronously wtr to shuffle job or mapper. Key: IGNITE-4272 URL:

[jira] [Created] (IGNITE-4271) Hadoop messages must use "direct marshallable" infrastructure.

Vladimir Ozerov created IGNITE-4271: --- Summary: Hadoop messages must use "direct marshallable" infrastructure. Key: IGNITE-4271 URL: https://issues.apache.org/jira/browse/IGNITE-4271 Project: Ignite

Start Contributing

Hello everybody! I want to contribute this project. -- Best wishes, Amelchev Nikita

[jira] [Created] (IGNITE-4270) Hadoop: optionally stripe mapper output for every partition.

Vladimir Ozerov created IGNITE-4270: --- Summary: Hadoop: optionally stripe mapper output for every partition. Key: IGNITE-4270 URL: https://issues.apache.org/jira/browse/IGNITE-4270 Project: Ignite

Re: Apache Ignite 1.8 Release

Folks, Yesterday it'd been agreed with Sergi that DML branch is now good to be included into 1.8 branch that is to be created. Minor review fixes, should they be made, and test fixes will be incorporated into 1.8 as separate patches later. Also, it'd been agreed that, in order to deliver these