Re: affinityRun() and affinityCall() (JIRA ticket)

Hi, We should assign the ticket to you. Can you please send your Jira username here (you can create one)? This way I will add you to a list of Ignite contributors in Jira and assign the ticket to you. D. On Wed, Jan 27, 2016 at 9:13 AM, Dood@ODDO wrote: > Hello, > > I am

Re: Check list for test implementation

Great start in improving the quality of JUnit testing in Ignite. It would be much better to put it in a table format, rather than list. I think, given the breadth of the tests listed, it will be almost impossible to follow this list for every fix or feature. Instead, we should provide an

Re: Proxy serialization issue

Who was originally responsible for fixing the Proxy serialization issue? On Wed, Jan 27, 2016 at 4:07 AM, Denis Magda wrote: > Igniters, > > A end user reported on the issue related to proxy > serialization/deserialization > https://issues.apache.org/jira/browse/IGNITE-2450

[jira] [Created] (IGNITE-2482) Unsaved changes confirmation partially does not work

Alexey Kuznetsov created IGNITE-2482: Summary: Unsaved changes confirmation partially does not work Key: IGNITE-2482 URL: https://issues.apache.org/jira/browse/IGNITE-2482 Project: Ignite

[jira] [Created] (IGNITE-2483) Cache metrics bugs

Valentin Kulichenko created IGNITE-2483: --- Summary: Cache metrics bugs Key: IGNITE-2483 URL: https://issues.apache.org/jira/browse/IGNITE-2483 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-2484) Performance: Cache compiled queries

Pavel Tupitsyn created IGNITE-2484: -- Summary: Performance: Cache compiled queries Key: IGNITE-2484 URL: https://issues.apache.org/jira/browse/IGNITE-2484 Project: Ignite Issue Type:

[GitHub] ignite pull request: IGNITE-2429: Added examples for the ODBC.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/430 IGNITE-2429: Added examples for the ODBC. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-2429 Alternatively you can

[jira] [Created] (IGNITE-2480) Optimization: Typed FieldsQueryCursor

Pavel Tupitsyn created IGNITE-2480: -- Summary: Optimization: Typed FieldsQueryCursor Key: IGNITE-2480 URL: https://issues.apache.org/jira/browse/IGNITE-2480 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-2485) tem.swapSpaceSpi[swapKind] is undefined

Pavel Konstantinov created IGNITE-2485: -- Summary: tem.swapSpaceSpi[swapKind] is undefined Key: IGNITE-2485 URL: https://issues.apache.org/jira/browse/IGNITE-2485 Project: Ignite Issue

Re: Ignite documentation: keep 1.6 docs in sync with 1.5

There is no easy way other than the same old copy-n-paste. To my knowledge, readme team is working on automating this process. D. On Wed, Jan 27, 2016 at 4:25 AM, Denis Magda wrote: > Igniters, > > Some of you have already been working on features that will be available >

[GitHub] ignite pull request: IGNITE-2465: Assertion in load cache closure ...

GitHub user ashutakGG opened a pull request: https://github.com/apache/ignite/pull/431 IGNITE-2465: Assertion in load cache closure (a race fixed) https://issues.apache.org/jira/browse/IGNITE-2465. You can merge this pull request into a Git repository by running: $ git pull

affinityRun() and affinityCall() (JIRA ticket)

Hello, I am playing with https://issues.apache.org/jira/browse/IGNITE-1144 as introduction to hacking on Ignite. I am not a Java developer by day but have experience writing code in various languages. This is my first in-depth exposure to Ignite internals (have lightly used it as a user in a

Check list for test implementation

Guys, While reviewing tests and production code we often see that developers do not add full test set to entirely cover all the aspects of a new feature or a fix. So, it seems to be very handy to have some kind of checklist for contributors and reviewers to follow. Here is the link -

Re: MyBatis and Apache Ignite integration

Hi Denis, and people from the ignite project. I have just created an empty project at Github for the integration: https://github.com/mybatis/ignite-cache As we spoke before, the interface is really simple. Probably we may have gone too far with the simplicity because some things need to be

Re: affinityRun() and affinityCall() (JIRA ticket)

Hi, Both GridCacheQueueAdapter and GridCacheSetImpl have a reference to GridCacheContext which represents the underlying cache for the data structure. GridCacheContext.name() will give you the correct cache name that you can use when calling affinityRun method. -Val On Wed, Jan 27, 2016 at 9:13

Re: affinityRun() and affinityCall() (JIRA ticket)

On Wed, Jan 27, 2016 at 5:48 PM, Dmitriy Setrakyan wrote: > > > On Wed, Jan 27, 2016 at 4:36 PM, Dood@ODDO wrote: > >> On 1/27/2016 5:33 PM, Dmitriy Setrakyan wrote: >> >>> Hi, >>> >>> We should assign the ticket to you. Can you please send your Jira

Proxy serialization issue

Igniters, A end user reported on the issue related to proxy serialization/deserialization https://issues.apache.org/jira/browse/IGNITE-2450 Could someone experienced in marshalling take a look at this? Seems that the original proxy related issue wasn't fully fixed. -- Denis

[GitHub] ignite pull request: ignite-2408

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

Re: ignite cache process entry should inject source?

Hi Wei Jiang, In my understanding you should persuade them to a valid design ;) -- Denis On 1/26/2016 4:50 PM, 姜 为 wrote: Hi Denis, Yes , I can change the way to do this. But my business follows MVC paradigm it will be very bloated. Hope can provide an option to do

Ignite documentation: keep 1.6 docs in sync with 1.5

Igniters, Some of you have already been working on features that will be available in the next release 1.6 and adding documentation to the doc versioned 1.6. [1] In the same time the community improves docs for version 1.5 (Hadoop + IGFS, queries, etc.). These changes are not reflected

[jira] [Created] (IGNITE-2467) Check box [Enable peer class loading] on [Class deployment] group should disable fields

Alexey Kuznetsov created IGNITE-2467: Summary: Check box [Enable peer class loading] on [Class deployment] group should disable fields Key: IGNITE-2467 URL: https://issues.apache.org/jira/browse/IGNITE-2467

[jira] [Created] (IGNITE-2468) Continuous query is no longer deployed when node, that deployed it initially, leaves topology

Denis Magda created IGNITE-2468: --- Summary: Continuous query is no longer deployed when node, that deployed it initially, leaves topology Key: IGNITE-2468 URL: https://issues.apache.org/jira/browse/IGNITE-2468

Re: Ignite Readme.IO UX issue

Hi: I have seen the changes in the document. I also found that part of the DataGrid has added a new section called "Lock". I maintain manual approach is, first from github document backup find changes, then according to the change point to find the online version of the difference and

[jira] [Created] (IGNITE-2469) ODBC: Remove OdbcProtocolHandler.

Vladimir Ozerov created IGNITE-2469: --- Summary: ODBC: Remove OdbcProtocolHandler. Key: IGNITE-2469 URL: https://issues.apache.org/jira/browse/IGNITE-2469 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-2459) Validation for java reserved keywords is not working

Alexey Kuznetsov created IGNITE-2459: Summary: Validation for java reserved keywords is not working Key: IGNITE-2459 URL: https://issues.apache.org/jira/browse/IGNITE-2459 Project: Ignite

[jira] [Created] (IGNITE-2461) cannot edit address in discovery settings in cluster

Pavel Konstantinov created IGNITE-2461: -- Summary: cannot edit address in discovery settings in cluster Key: IGNITE-2461 URL: https://issues.apache.org/jira/browse/IGNITE-2461 Project: Ignite

[jira] [Created] (IGNITE-2464) Text for validation tooltips should be configurable or specified.

Alexey Kuznetsov created IGNITE-2464: Summary: Text for validation tooltips should be configurable or specified. Key: IGNITE-2464 URL: https://issues.apache.org/jira/browse/IGNITE-2464 Project:

[GitHub] ignite pull request: IGNITE-2453 Fixed single primary and single b...

GitHub user VladimirErshov opened a pull request: https://github.com/apache/ignite/pull/427 IGNITE-2453 Fixed single primary and single backup failure cause NPE … …at future for backup You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-2466) OutOfMemory when OFFHEAP_TIRED mode is used

Denis Magda created IGNITE-2466: --- Summary: OutOfMemory when OFFHEAP_TIRED mode is used Key: IGNITE-2466 URL: https://issues.apache.org/jira/browse/IGNITE-2466 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-2463) UI should expand groups and scroll focus to first invalid field on Save button click

Alexey Kuznetsov created IGNITE-2463: Summary: UI should expand groups and scroll focus to first invalid field on Save button click Key: IGNITE-2463 URL: https://issues.apache.org/jira/browse/IGNITE-2463

[jira] [Created] (IGNITE-2462) issue with empty address list in discovery on clusters page

Pavel Konstantinov created IGNITE-2462: -- Summary: issue with empty address list in discovery on clusters page Key: IGNITE-2462 URL: https://issues.apache.org/jira/browse/IGNITE-2462 Project:

[GitHub] ignite pull request: IGNITE-1786: Review-related fixes and refacto...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/426 --- 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-2460) issue with mandatory fields

Pavel Konstantinov created IGNITE-2460: -- Summary: issue with mandatory fields Key: IGNITE-2460 URL: https://issues.apache.org/jira/browse/IGNITE-2460 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-2465) Assertion in load cache closure

Denis Magda created IGNITE-2465: --- Summary: Assertion in load cache closure Key: IGNITE-2465 URL: https://issues.apache.org/jira/browse/IGNITE-2465 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-2471) LINQ provider foundation

Pavel Tupitsyn created IGNITE-2471: -- Summary: LINQ provider foundation Key: IGNITE-2471 URL: https://issues.apache.org/jira/browse/IGNITE-2471 Project: Ignite Issue Type: Sub-task

[GitHub] ignite pull request: IGNITE-2273

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

[jira] [Created] (IGNITE-2470) AtomicConfiguration is necessary to add an attribute, similar nodeFilter

liyujue created IGNITE-2470: --- Summary: AtomicConfiguration is necessary to add an attribute, similar nodeFilter Key: IGNITE-2470 URL: https://issues.apache.org/jira/browse/IGNITE-2470 Project: Ignite

[jira] [Created] (IGNITE-2472) Aggregate functions

Pavel Tupitsyn created IGNITE-2472: -- Summary: Aggregate functions Key: IGNITE-2472 URL: https://issues.apache.org/jira/browse/IGNITE-2472 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-2473) Numeric functions

Pavel Tupitsyn created IGNITE-2473: -- Summary: Numeric functions Key: IGNITE-2473 URL: https://issues.apache.org/jira/browse/IGNITE-2473 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-2474) String functions

Pavel Tupitsyn created IGNITE-2474: -- Summary: String functions Key: IGNITE-2474 URL: https://issues.apache.org/jira/browse/IGNITE-2474 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-2475) DateTime support and functions

Pavel Tupitsyn created IGNITE-2475: -- Summary: DateTime support and functions Key: IGNITE-2475 URL: https://issues.apache.org/jira/browse/IGNITE-2475 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-2478) Field queries (projections)

Pavel Tupitsyn created IGNITE-2478: -- Summary: Field queries (projections) Key: IGNITE-2478 URL: https://issues.apache.org/jira/browse/IGNITE-2478 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-2477) Nested queries

Pavel Tupitsyn created IGNITE-2477: -- Summary: Nested queries Key: IGNITE-2477 URL: https://issues.apache.org/jira/browse/IGNITE-2477 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-2476) Joins and Unions

Pavel Tupitsyn created IGNITE-2476: -- Summary: Joins and Unions Key: IGNITE-2476 URL: https://issues.apache.org/jira/browse/IGNITE-2476 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-2479) Missed continuous query notification when cache listener is used

Denis Magda created IGNITE-2479: --- Summary: Missed continuous query notification when cache listener is used Key: IGNITE-2479 URL: https://issues.apache.org/jira/browse/IGNITE-2479 Project: Ignite