[jira] [Created] (IGNITE-4507) Hadoop: allow direct shuffle mode when combiner is set

Vladimir Ozerov created IGNITE-4507: --- Summary: Hadoop: allow direct shuffle mode when combiner is set Key: IGNITE-4507 URL: https://issues.apache.org/jira/browse/IGNITE-4507 Project: Ignite

Re: IGNITE-4487 - NPE on query execution

I think that If fallbacks(...) returns an empty nodes collection, then we should fail with an exception. 2016-12-28 22:06 GMT+03:00 Denis Magda : > Alexander, added you to the contributors list. Please check that you can > assign the ticket on yourself. > > — > Denis > > > On Dec 28, 2016, at 2:1

Error in JDBC store

Hi all! According to this thread [1] in JDBC store configuration: 1. Map key and value fields to the same columns in DB. 2. Try to update data. 3. Got invalid SQL. Let's see an pseudocode example of described use case. KeyClass { field1; field2; field3 }, ValClass { field1; field2; field3 } Map

[jira] [Created] (IGNITE-4508) CacheQueryExample and CacheClientBinaryQueryExample print class name and hash instead of smth meaningful

Ksenia Rybakova created IGNITE-4508: --- Summary: CacheQueryExample and CacheClientBinaryQueryExample print class name and hash instead of smth meaningful Key: IGNITE-4508 URL: https://issues.apache.org/jira/browse

PageMemory approach for Ignite 2.0

Folks, I pushed an initial implementation of IGNITE-3477 to ignite-3477 branch for community review and further discussion. Note that the implementation lacks the following features: - On-heap deserialized values cache - Full LOCAL cache support - Eviction policies - Multiple memory pools -

[jira] [Created] (IGNITE-4509) SQL: query with condition on affinity columns and without joins and subqueries can be replaced with GET

Vladimir Ozerov created IGNITE-4509: --- Summary: SQL: query with condition on affinity columns and without joins and subqueries can be replaced with GET Key: IGNITE-4509 URL: https://issues.apache.org/jira/browse/

Re: PageMemory approach for Ignite 2.0

I agree, we should fix all the outstanding issues and resolve the performance problems before merging it into 2.0 Sergi 2016-12-29 12:37 GMT+03:00 Alexey Goncharuk : > Folks, > > I pushed an initial implementation of IGNITE-3477 to ignite-3477 branch for > community review and further discussion

[jira] [Created] (IGNITE-4510) SQL: co-located query may calculate target partition in advance in some cases

Vladimir Ozerov created IGNITE-4510: --- Summary: SQL: co-located query may calculate target partition in advance in some cases Key: IGNITE-4510 URL: https://issues.apache.org/jira/browse/IGNITE-4510 P

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

I am OK with CLUSTER_REGION_ID. However I would like this name - DISCOVERY_REGION_ID - more. >> Do you think we will ever care about the order of nodes within the same region, e.g. does the order of nodes within the same rack matter? >> I think this is too much, but if you care you still can. Ima

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

Guys, I have updated the ticket. Alexander Menshikov, when do you expect the implementation to be finished?

[jira] [Created] (IGNITE-4511) Set QueryIndexType.SORTED by default for an index

Steve Hostettler created IGNITE-4511: Summary: Set QueryIndexType.SORTED by default for an index Key: IGNITE-4511 URL: https://issues.apache.org/jira/browse/IGNITE-4511 Project: Ignite I

Re: IGNITE-4487 - NPE on query execution

Alexey, I'm already make pull request where throw exception in that place. https://github.com/apache/ignite/pull/1388/commits 2016-12-29 11:16 GMT+03:00 Alexey Goncharuk : > I think that If fallbacks(...) returns an empty nodes collection, then we > should fail with an exception. > > 2016-12-28

[jira] [Created] (IGNITE-4512) Doesnt work sql-delete benchmark

Ilya Suntsov created IGNITE-4512: Summary: Doesnt work sql-delete benchmark Key: IGNITE-4512 URL: https://issues.apache.org/jira/browse/IGNITE-4512 Project: Ignite Issue Type: Bug C

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

I think that in the weeks after the 'new year' holidays or sooner. 2016-12-29 13:28 GMT+03:00 Yakov Zhdanov : > Guys, I have updated the ticket. > > Alexander Menshikov, when do you expect the implementation to be finished? >

Re: About RoundRobinLoadBalancingSpi

Val， Javadoc also need to be modified. 在 2016/12/29 00:08, Valentin Kulichenko 写道: Hi, Thanks for pointing this out. I fixed the documentation. -Val On Tue, Dec 27, 2016 at 7:50 PM, 李玉珏 wrote: Hi， In RoundRobinLoadBalancingSpi，according to the description of the document,per-task mode

Re: IGNITE-4487 - NPE on query execution

Alexander, thanks. Please move the ticket from “open” into “patch available” state in JIRA and run the tests on TeamCity. Refer to the details covered there https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-1.CreateGitHubpull-request

Re: PageMemory approach for Ignite 2.0

Alex, > On Dec 29, 2016, at 1:37 AM, Alexey Goncharuk > wrote: > > The subject of this discussion is to determine whether the PageMemory > approach is a way to go, because the this implementation is almost 2x > slower than current 2.0 branch. What is the main reason for that? Some architectur

Re: PageMemory approach for Ignite 2.0

Denis, this is not "dreaming". We can't have a release with less features than 1.8. We can only add features, not subtract. Dmitriy > On Dec 29, 2016, at 9:49 AM, Denis Magda wrote: > > Alex, > >> On Dec 29, 2016, at 1:37 AM, Alexey Goncharuk >> wrote: >> >> The subject of this discussio

Re: Error in JDBC store

Hi Dmitry, My opinion is that this is not a valid case and we should throw an exception on cache startup if two Java fields are mapped to the same DB field. Even if user needs such duplication on objects level (which I also doubt, BTW), the mapping in the store must be correct. -Val On Thu, Dec

Re: About RoundRobinLoadBalancingSpi

Fixed. On Thu, Dec 29, 2016 at 6:08 AM, 李玉珏@163 <18624049...@163.com> wrote: > Val， > > Javadoc also need to be modified. > > > > 在 2016/12/29 00:08, Valentin Kulichenko 写道: > >> Hi, >> >> Thanks for pointing this out. I fixed the documentation. >> >> -Val >> >> On Tue, Dec 27, 2016 at 7:50 PM, 李

[jira] [Created] (IGNITE-4513) Improve DEBUG logging for continuous queries

Valentin Kulichenko created IGNITE-4513: --- Summary: Improve DEBUG logging for continuous queries Key: IGNITE-4513 URL: https://issues.apache.org/jira/browse/IGNITE-4513 Project: Ignite I

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

CC-ing Apache Ignite dev@ in the loop. Igniters, PMC members had a talk with Sally Khudairi who represents ASF Marketing & Publicity group. Sally, thanks a lot for finding a time to jump on the call. One of the main topics of the call was our latest 1.8.0 release. It was agreed that Sally wou

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

Thanks, Denis. Hello, everyone! Indeed, I think releasing a "highlight" announcement makes sense here, and I'll be happy to work with you over the next week or so to get that drafted. And thanks in advance, Roman Shtykh, for acting as project spokesperson in your role as release manager. Particip

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

Sally, looks like you got confused with this > On Dec 29, 2016, at 2:38 PM, Sally Khudairi wrote: > > And thanks in advance, Roman Shtykh, for acting as project spokesperson in > your role as release manager. Participation from the community at-large is > greatly appreciated! Roman have never

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

Boop! Sorry about that...indeed, I wrote Roman's name in my notes next to "1.8 release manager?" and clearly combined the two. Apologies for alarming you. But that is a good hint, Denis Cheers,Sally [From the mobile; please excuse top-posting, spelling/spacing errors, and brevity] On T

Re: Google Summer Of Code 2017

Igor R., is there anything that can be improved & refined in the existed integration of Ignite and Cassandra and outsourced to Google Summer of Code? — Denis > On Dec 22, 2016, at 10:29 AM, Denis Magda wrote: > > This is great! > > So, we already have three mentors in total (Val, Dmitriy, De

[GitHub] ignite pull request #1395: ignite-4496

GitHub user akuramshingg opened a pull request: https://github.com/apache/ignite/pull/1395 ignite-4496 Review all logging for sensitive data leak You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4496