Re: ignite-2310

[Dmitriy Setrakyan]

Thanks Taras, I have added my comments in the ticket.

On Thu, Jul 7, 2016 at 5:44 AM, Taras Ledkov  wrote:

> Igniters,
>
> The issue https://issues.apache.org/jira/browse/IGNITE-2310 is updated
> with comment
> about the changes at the IgniteCompute. Please comment the ticket.
>
> The changed javadoc of the affinityRun/Call is available to review at the
> branch
>
> https://github.com/gridgain/apache-ignite/blob/ignite-2310/modules/core/src/main/java/org/apache/ignite/IgniteCompute.java#L123
>
> 07.07.2016 14:13, Dmitriy Setrakyan пишет:
>
> Taras, it is very difficult to review API changes this way. Can you please
>> provide additional APIs in the ticket?
>>
>> Also, we should add documentation about reserving partitions as well. To
>> my
>> knowledge, this feature ensures that a partition will not be migrated
>> while
>> affinityRun/Call is executed, right?
>>
>> On Thu, Jul 7, 2016 at 3:02 AM, Taras Ledkov 
>> wrote:
>>
>> Igniters,
>>>
>>> Please take a look at the next proposal of changes at
>>> IgniteCompute.affinityRun / affinityCall:
>>>
>>>
>>>
>>> https://github.com/gridgain/apache-ignite/commit/c57f009c44e07240fc8c8e6feed3271c63f31664#diff-b276b8e6e14915f9e5f2f5daeeddec8a
>>>
>>> So, two methods is added affinityRun and affinityCall. There is
>>> additional
>>> parameter Collection of extra caches names.
>>> An affinity job without the extra caches reserves only one partition
>>> (that
>>> contains affinity key) of the affinity cache.
>>> An affinity job with the extra caches parameter reserves the partitions
>>> (similar to affinity partition) of all extra caches.
>>>
>>>
>>> 06.07.2016 15:18, Semyon Boikov wrote:
>>>
>>> I think we should detect such situation and throw exception. As I
 remember
 for cross cache qieries we throw exception if caches have different
 partitions distribution.

 On Wed, Jul 6, 2016 at 3:14 PM, Yakov Zhdanov 
 wrote:

 Guys, this does not work in general case. If you provide more than one

> partition you can end up with a situation when they reside on more than
> one
> node.
>
> --Yakov
>
> 2016-07-06 13:50 GMT+03:00 Vladimir Ozerov :
>
> If we add "partsToLock" to job execute request, then why we allow it
> only
>
>> for "affinity" methods? We can resort to "with" semantics instead:
>>
>> IgniteCompute.*withPartitionsToLock*(...).affinityRun();
>>
>> On Wed, Jul 6, 2016 at 12:23 PM, Taras Ledkov 
>> wrote:
>>
>> Igniters,
>>
>>> Lets discuss the changes of public API at the IgniteCompute.
>>> The new methods affinityRun & affinityCall is added by working on
>>> IGNITE-2310.
>>>
>>> https://issues.apache.org/jira/browse/IGNITE-2310
>>>
>>> Please take a look at the signature of the new methods:
>>>
>>>
>>>
>>>
>>>
> https://github.com/gridgain/apache-ignite/commit/991fb60f563ee1630152ca0159d04b4969f883bf#diff-b276b8e6e14915f9e5f2f5daeeddec8a
>
> void affinityRun(@Nullable String cacheName, Object affKey,
>> IgniteRunnable
>>
>> job, Map partsToLock)
>>>
>>> The parameter Map partsToLock is added.
>>> Map contains the pairs of the cache name and array of partitions that
>>>
>>> must
>>
>> be reserved on the target node before job execution.
>>>
>>> Dmitry, colleagues, please comment or approve.
>>>
>>> --
>>> Taras Ledkov
>>> Mail-To: tled...@gridgain.com
>>>
>>>
>>>
>>> --
>>> Taras Ledkov
>>> Mail-To: tled...@gridgain.com
>>>
>>>
>>>
> --
> Taras Ledkov
> Mail-To: tled...@gridgain.com
>
>

Re: kick off a discussion

[Dmitriy Setrakyan]

Thanks Sasha!

Resending to the dev list.

D.

On Fri, Jul 8, 2016 at 2:02 PM, Alexandre Boudnik 
wrote:

> Apache Ignite a great platform but it lacks of certain capabilities,
> which are common in RDMS world, such as:
> - Consistent on-line backup for data on entire cluster (or for
> specified set of caches)
> - Hierarchal snapshots for specified set caches
> - Transaction log
> - Restore cluster state as of certain point in time
> - Rolling forward from snapshot with ability to filter/modify transactions
> - Asynchronous replication based either on log shipment or snapshot
> shipment
> -- Between clusters
> -- Continues data export to let’s say RDMS
> It is also a necessity to reduce cold start time for huge clusters
> with strict SLAs.
>
> I'll put some implementation ideas in JIRA later on. I believe that
> this list is far from being complete, but I want the community to
> discuss these abovementioned use cases.
>
> --Sasha
>

[jira] [Created] (IGNITE-3457) Active Store

[Alexandre Boudnik (JIRA)]

Alexandre Boudnik created IGNITE-3457:
-

 Summary: Active Store
 Key: IGNITE-3457
 URL: https://issues.apache.org/jira/browse/IGNITE-3457
 Project: Ignite
  Issue Type: New Feature
  Components: general
Reporter: Alexandre Boudnik
Assignee: Alexandre Boudnik


To address missing features, such as backup/restore, snapshot, replication, and 
continues export



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request #864: Ignite-3055

[vldpyatkov]

GitHub user vldpyatkov opened a pull request:

https://github.com/apache/ignite/pull/864

Ignite-3055



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/vldpyatkov/ignite ignite-3055

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/864.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #864






---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-3456) Make sure EntryProcessor is always running on a OWNING partition

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-3456:


 Summary: Make sure EntryProcessor is always running on a OWNING 
partition
 Key: IGNITE-3456
 URL: https://issues.apache.org/jira/browse/IGNITE-3456
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Reporter: Alexey Goncharuk


Let's say I need to maintain some sort of an aggregate function over a 
partition. This aggregate is maintained using an entry processor, and before an 
update this entry processor queries this local aggregate.

If an entry processor is applied on a partition with a MOVING state, the state 
of the local aggregate is not valid because not all data has been preloaded. If 
entry processor is applied on an OWNING partition, the result is guaranteed to 
be correct.

Given that we have implemented late affinity assignment when a new node is 
assigned primary only when rebalancing is finished, this should be already 
maintained. We just need to add tests verifying the partition state in 
EntryProcessor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request #863: ignite-3412

[ascherbakoff]

GitHub user ascherbakoff opened a pull request:

https://github.com/apache/ignite/pull/863

ignite-3412

Client instance hangs on close.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ascherbakoff/ignite ignite-3412

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/863.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #863


commit 84583756b1c49a78471877ee306fbd11f047ffeb
Author: ascherbakoff 
Date:   2016-04-11T14:35:40Z

IGNITE-2941

commit fbb3adf7df16d8f938d03909a7d88d614f411937
Author: Aleksei Scherbakov 
Date:   2016-04-15T16:27:39Z

Merge remote-tracking branch 'upstream/master'

commit 4058702ac6a8313b5a7dd2af11da2588c1b5856b
Author: Aleksei Scherbakov 
Date:   2016-05-12T09:36:01Z

Merge remote-tracking branch 'origin/master'

# Conflicts:
#   modules/core/src/main/java/org/apache/ignite/internal/IgnitionEx.java

commit b68431a4bb76759f20e556dba2b263e1323da062
Author: Alexei Scherbakov 
Date:   2016-05-12T09:52:54Z

Merge remote-tracking branch 'upstream/master'

commit 7a3ec6340ad85f4ac9ab079f81da15dd2c443050
Author: Aleksei Scherbakov 
Date:   2016-05-12T10:18:32Z

Merge with upstream

commit 3849b351d33f2e33db918e2a2215a6e5868b1399
Author: Alexei Scherbakov 
Date:   2016-05-13T09:49:10Z

Merge remote-tracking branch 'upstream/master'

commit 7afc5d8d6402f690c6bc4f223de9d9d83dc108f2
Author: Aleksei Scherbakov 
Date:   2016-05-16T09:33:57Z

Merge branch 'master' of https://github.com/apache/ignite

commit 447db34bba948a09bc0f0361a56cbd35772329ff
Author: Aleksei Scherbakov 
Date:   2016-05-20T12:04:35Z

Merge branch 'master' of https://github.com/apache/ignite

commit 71cb9286d1bf54e3ded36f815d0343d593025953
Author: Aleksei Scherbakov 
Date:   2016-05-23T16:16:53Z

Merge branch 'master' of https://github.com/apache/ignite

commit d9668bd0e30b0891ba01d9323cfbaa80d26e310f
Author: Aleksei Scherbakov 
Date:   2016-05-24T14:36:14Z

Merge branch 'master' of https://github.com/apache/ignite

commit fe0987bc85cc23a8e3eae12a284369e7eefa384d
Author: Aleksei Scherbakov 
Date:   2016-05-27T10:34:24Z

Merge branch 'master' of https://github.com/apache/ignite

commit d67bf92fa4040f5f21f66113db4b8800cb998152
Author: Aleksei Scherbakov 
Date:   2016-06-17T10:04:56Z

Merge branch 'master' of https://github.com/apache/ignite

commit 9de33957e5e0ca5ed5a6e11fd3251a1da984742a
Author: Aleksei Scherbakov 
Date:   2016-07-04T08:12:51Z

Merge branch 'master' of https://github.com/apache/ignite

commit 37b0a68f23d9ab9f1483f9a8344129ac051f821c
Author: Aleksei Scherbakov 
Date:   2016-07-04T13:53:54Z

Merge branch 'master' of https://github.com/apache/ignite

commit fff447d817e025bb91d1d442ac5f27b892e205cc
Author: Aleksei Scherbakov 
Date:   2016-07-06T09:13:10Z

Merge branch 'master' of https://github.com/apache/ignite

commit b506344d7670945eb1137b41248a9da15e6b506b
Author: Aleksei Scherbakov 
Date:   2016-07-08T14:29:30Z

IGNITE-3412 Client instance hangs on close.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Ignite 3227

[Saikat Maitra]

Thank you Alexey !!!

Regards
Saikat

On Fri, Jul 8, 2016 at 7:41 AM, Alexey Goncharuk  wrote:

> Saikat,
>
> I merged your PR to master. Thanks for the contribution!
>
> 2016-07-05 16:46 GMT-07:00 Dmitriy Setrakyan :
>
> > I think we should add only 1 new method:
> >
> > long sizeLong(int partId, CachePeekMode peekMode)
> >
> > D.
> >
> > On Tue, Jul 5, 2016 at 3:24 PM, Alexander Paschenko <
> > alexander.a.pasche...@gmail.com> wrote:
> >
> > > Alexey in Jira
> > >
> >
> https://issues.apache.org/jira/browse/IGNITE-3227?focusedCommentId=15360787
> > > suggested that we remove int sized methods from CacheProxy, and he has
> > > indeed removed them, but IgniteCache has such new methods too. Should
> > > we let them be or maybe it would be better to get rid of them? Please
> > > advise. Dmitriy Setrakyan, your opinion on the matter is of particular
> > > interest.
> > >
> > > 2016-07-04 19:30 GMT+03:00 Saikat Maitra :
> > > > Thanks a lot Alexey.
> > > >
> > > > Regards
> > > > Saikat
> > > >
> > > > On Mon, Jul 4, 2016 at 12:01 PM, Alexey Goncharuk <
> > > > alexey.goncha...@gmail.com> wrote:
> > > >
> > > >> Saikat,
> > > >>
> > > >> Thanks for the contribution. I will make some minor changes to your
> > > patch
> > > >> and push it to master soon.
> > > >>
> > > >> 2016-06-26 9:57 GMT-07:00 Saikat Maitra :
> > > >>
> > > >> > Hi Alexey, Ilya
> > > >> >
> > > >> > As discussed I have made the changes in the PR[1]. Please review
> and
> > > let
> > > >> me
> > > >> > know any feedback.
> > > >> >
> > > >> > [1] https://github.com/apache/ignite/pull/815
> > > >> > [2] https://issues.apache.org/jira/browse/IGNITE-3227
> > > >> >
> > > >> >
> > > >> > Regards
> > > >> > Saikat
> > > >> >
> > > >> > On Mon, Jun 20, 2016 at 10:40 PM, Saikat Maitra <
> > > saikat.mai...@gmail.com
> > > >> >
> > > >> > wrote:
> > > >> >
> > > >> > > Sure Alexey,
> > > >> > >
> > > >> > > Thank you
> > > >> > > Saikat
> > > >> > >
> > > >> > > On Mon, Jun 20, 2016 at 10:36 PM, Alexey Goncharuk <
> > > >> > > alexey.goncha...@gmail.com> wrote:
> > > >> > >
> > > >> > >> Saikat,
> > > >> > >>
> > > >> > >> Please also correct the test to check new methods for
> PARTITIONED
> > > and
> > > >> > >> REPLICATED cache - I see that you only test them for local
> cache
> > > and
> > > >> > >> partition 0 (I added a comment to the ticket).
> > > >> > >>
> > > >> > >> 2016-06-20 9:17 GMT-07:00 Saikat Maitra <
> saikat.mai...@gmail.com
> > >:
> > > >> > >>
> > > >> > >> > Thank you Ilya, I will review and update PR accordingly.
> > > >> > >> >
> > > >> > >> > Regards
> > > >> > >> > Saikat
> > > >> > >> >
> > > >> > >> > On Mon, Jun 20, 2016 at 8:36 PM, Ilya Lantukh <
> > > >> ilant...@gridgain.com>
> > > >> > >> > wrote:
> > > >> > >> >
> > > >> > >> > > Hi Saikat,
> > > >> > >> > >
> > > >> > >> > > I've added a comment to the jira ticket regarding
> > > implementation
> > > >> of
> > > >> > >> > > GridCacheAdapter#localSizeLong(int partition,
> CachePeekMode[]
> > > >> > >> peekModes)
> > > >> > >> > > method.
> > > >> > >> > >
> > > >> > >> > > On Sat, Jun 18, 2016 at 12:19 PM, Saikat Maitra <
> > > >> > >> saikat.mai...@gmail.com
> > > >> > >> > >
> > > >> > >> > > wrote:
> > > >> > >> > >
> > > >> > >> > > > Hi
> > > >> > >> > > >
> > > >> > >> > > > I have raised the PR[1] for the jira ticket Ignite 3227
> [2]
> > > and
> > > >> > >> wanted
> > > >> > >> > to
> > > >> > >> > > > discuss further on this issue.
> > > >> > >> > > >
> > > >> > >> > > > 1. I am running 2 nodes cluster and running in client
> mode
> > > >> another
> > > >> > >> node
> > > >> > >> > > for
> > > >> > >> > > > functional test. I added 20 keys and keys are distributed
> > in
> > > 2
> > > >> > >> nodes as
> > > >> > >> > > 11
> > > >> > >> > > > keys in node 1 and 9 keys in node 2. When I am printing
> > > >> partition
> > > >> > 1
> > > >> > >> > size
> > > >> > >> > > > and partition 2 size I can get correct values but incase
> I
> > > >> provide
> > > >> > >> some
> > > >> > >> > > > other partition like 5 I am observing that I am getting
> 11
> > as
> > > >> > value.
> > > >> > >> > > >
> > > >> > >> > > > 2. I have added unit test testpartitionsize() similar to
> > > >> > testSize()
> > > >> > >> but
> > > >> > >> > > > similar tests are failing for both the tests. Need
> further
> > > >> > >> > investigation
> > > >> > >> > > on
> > > >> > >> > > > the same.
> > > >> > >> > > >
> > > >> > >> > > >
> > > >> > >> > > > Regards
> > > >> > >> > > > Saikat
> > > >> > >> > > >
> > > >> > >> > > > [1] https://github.com/apache/ignite/pull/815
> > > >> > >> > > > [2] https://issues.apache.org/jira/browse/IGNITE-3227
> > > >> > >> > > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > > --
> > > >> > >> > > Best regards,
> > > >> > >> > > Ilya
> > > >> > >> > >
> > > >> > >> >
> > > >> > >>
> > > >> > >
> > > >> > >
> > > >> >
> > > >>
> > >
> 

[GitHub] ignite pull request #862: Ignite 3440

[dmagda]

GitHub user dmagda opened a pull request:

https://github.com/apache/ignite/pull/862

Ignite 3440



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-3440

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/862.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #862


commit 1c04005c08ae7ca2006d6f2f687a95c2638c73fc
Author: nikolay_tikhonov 
Date:   2016-03-25T12:22:37Z

IGNITE-GG-11048 Added tests.

commit 53a87290fe028e12a81058fc4b2f2f2341395f9a
Author: Tikhonov Nikolay 
Date:   2016-03-25T16:49:31Z

Fixed tests (renamed test methods).

commit ce56625099b5253f8baf27bfbcff4682787a5ee1
Author: Anton Vinogradov 
Date:   2016-03-28T11:13:20Z

Query Suite separation : 1,2,3

commit 08f5981509711e65c0d4c6fc1209068f8958eb06
Author: vozerov-gridgain 
Date:   2016-03-28T09:24:16Z

Support optional IO policy resolver in DataStreamer.

commit 60e74618b310dafc28eb5f935859fed4ec87584c
Author: vozerov-gridgain 
Date:   2016-03-28T11:52:13Z

Merge remote-tracking branch 'upstream/gridgain-7.5.10' into gridgain-7.5.10

commit 9e84e508a394b790ef046cdcf2a015bcf853c064
Author: nikolay_tikhonov 
Date:   2016-03-28T13:59:56Z

Divide test suite.

commit d36a2e51e3aa3105dff73839c84e52a531fbd918
Author: Denis Magda 
Date:   2016-03-24T17:07:48Z

IGNITE-2849: BinaryObjectBuilder doesn't properly check metadata

commit 9e62b667e73396d3affbc4d1e62449d07d08ec8b
Author: Anton Vinogradov 
Date:   2016-03-29T11:56:21Z

 IGNITE-2801 Coordinator floods network with partitions full map exchange 
messages

commit 85a675b7bfbc54745ee9ce95d5786b5bae5be963
Author: iveselovskiy 
Date:   2016-01-18T14:28:42Z

IGNITE-1788: Removed duplicate check of a single invariant from 
IgfsProcessor.  This closes #221.

commit 0e753c38a986cbd46eb24845808ec1d0fc7d1dea
Author: dkarachentsev 
Date:   2016-02-10T09:38:43Z

IGNITE-2575: Added validation of IGFS endpoint port value. This closes #469.

commit 99028b509c736b79faac7fb8104b1bc3cfe30720
Author: vozerov-gridgain 
Date:   2016-03-03T09:56:55Z

IGFS: Minor refactoring.

commit 219238f2793a3f3f9f5705a065c67510c286df1c
Author: vozerov-gridgain 
Date:   2016-03-03T10:25:43Z

IGNITE-2754: IGFS: Created separate processor for listing remove operation.

commit ff5b68ca69050817794ef4b142c955a186e03de9
Author: vozerov-gridgain 
Date:   2016-03-14T07:19:23Z

IGNITE-2781: IGFS: Force "copyOnRead=false" for meta and data caches.

commit 37c4d508c9e40dcba274ae1625d7bf59bfeef144
Author: vozerov-gridgain 
Date:   2016-03-14T08:49:03Z

IGNITE-2810: IGFS: Striped trash directory to reduce contention during 
removals.

commit 54e6991cb1d0b68c4490dede603c9e3ba7cc3b9e
Author: vozerov-gridgain 
Date:   2016-03-14T09:05:39Z

IGNITE-2810: IGFS: Minor correction to IgfsUtils.isRootOrTrashId() method.

commit 8083391be726c2bbc27e018983ca713e4b25e2a2
Author: vozerov-gridgain 
Date:   2016-03-14T10:17:58Z

IGNITE-2814: IGFS: File lock/unlock/reserve operations are no longer 
require put/replace on cache. Thin entry processors are used instead.

commit a7c1f44420ae96f183abc2e17125f0c9aa0775d5
Author: vozerov-gridgain 
Date:   2016-03-14T12:57:28Z

IGNITE-2828: IGFS: Introduced processor for "updateTimes" operation.

commit ba30ddbc599d67f398ffba1263d174f5b58b4b7d
Author: thatcoach 
Date:   2016-03-15T17:46:13Z

IGNITE-2838: IGFS: Opimized format of IgfsListingEntry. Now it contains 
only file ID and boolean flag endicating whether this a directory or file.

commit 4f7e3c1c2e82596a26cec3b3587991ae18078b64
Author: vozerov-gridgain 
Date:   2016-03-16T06:14:49Z

IGNITE-2817: IGFS: Optimized "updateProperties" and several other cache 
operations. Reafactored IgfsMetaManager a bit to simplify work with cache.

commit 3e59321ef0ae1d936d94f8f804db45ceeff55844
Author: vozerov-gridgain 
Date:   2016-03-16T09:31:37Z

IGNITE-2842: IGFS: Optimized create/mkdirs operations with help of entry 
processors.

commit f57f3657b1da33abf28f885cd405780dabfd57e3
Author: vozerov-gridgain 
Date:   2016-03-16T10:22:07Z

IGNITE-2846: IGFS: Reworked IgfsMetaManager.updateInfo() operation to use 
"invoke" instead of "put".

commit 8a93c3bf1687e6f2de1a4391d95366d733a44a7d
Author: vozerov-gridgain 
Date:   2016-03-18T13:38:45Z

[jira] [Created] (IGNITE-3455) Entry placed on C++ side is not found on Java side

[Denis Magda (JIRA)]

Denis Magda created IGNITE-3455:
---

 Summary: Entry placed on C++ side is not found on Java side
 Key: IGNITE-3455
 URL: https://issues.apache.org/jira/browse/IGNITE-3455
 Project: Ignite
  Issue Type: Bug
  Components: cache, platforms
Reporter: Denis Magda
Assignee: Denis Magda
Priority: Blocker


If a custom key is used for cache values then the following scenario doesn't 
work:
- value is placed on C++ side;
- value is read on Java side (value is not found here).

Reverse direction is not workable as well.

HashCode is implemented properly in C++ and Java.

Fast debugging showed that a partition and primary node is calculated properly. 
Looks like that there is a serialization related issue that leads to the 
situation when "equals" fails during an object lookup.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request #858: Ignite 3413

[alexpaschenko]

Github user alexpaschenko closed the pull request at:

https://github.com/apache/ignite/pull/858


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

SQL engine related issues.

[Alexei Scherbakov]

Guys,

I've created two SQL related issues which recently arose in user list:
Correct me if we are already have something similar.

1) https://issues.apache.org/jira/browse/IGNITE-3453

I suppose it's H2 related issue and will be resolved after transition to
1.4 version,
which supports index hints.

2) https://issues.apache.org/jira/browse/IGNITE-3448

It looks like map-reduce query splitting related issue.

I think it's quite basic case and something has to be done about it.

What do you think ?

-- 

Best regards,
Alexei Scherbakov

[jira] [Created] (IGNITE-3453) Query engine picks incorrect index in certain configurations.

[Alexei Scherbakov (JIRA)]

Alexei Scherbakov created IGNITE-3453:
-

 Summary: Query engine picks incorrect index in certain 
configurations.
 Key: IGNITE-3453
 URL: https://issues.apache.org/jira/browse/IGNITE-3453
 Project: Ignite
  Issue Type: Bug
Reporter: Alexei Scherbakov
 Attachments: Example.java

Index selection depends on index name ordering, not the argument type.

Index 1 (name idx_1):
countryId:Integer, regionId:Integer, cityId:Integer

Index 2 (name idx_0):
countryId:Integer, regionId:Integer, nation:String

For query:
select id, countryId, cityId from Person where countryId=? and regionId=? and 
cityId=? params 1,1,1

the index 2 is picked incorrectly and only two first fields are used.

See full reproducer in the attachment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3452) We need to add a validation that pool size has value greater the zero

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-3452:
--

 Summary: We need to add a validation that pool size has value 
greater the zero
 Key: IGNITE-3452
 URL: https://issues.apache.org/jira/browse/IGNITE-3452
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov
Priority: Trivial


Currently I was able to enter MarshallerPoolSize=0 and got the exception on 
node start
{code}
java.lang.IllegalArgumentException
at 
java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1310)
at 
java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1233)
at 
org.apache.ignite.thread.IgniteThreadPoolExecutor.(IgniteThreadPoolExecutor.java:185)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1720)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1589)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042)
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:964)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:850)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:749)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:619)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
at org.apache.ignite.Ignition.start(Ignition.java:347)
at 
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Failed to start grid: null
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3451) Web console: Invalid results of SQL query in area chart

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-3451:
-

 Summary: Web console: Invalid results of SQL query in area chart
 Key: IGNITE-3451
 URL: https://issues.apache.org/jira/browse/IGNITE-3451
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.7
Reporter: Vasiliy Sisko


1) Run in demo mode and open SQL page.
2) Execute query:
{code}
SELECT p.name, count(*) AS cnt, 4 as num
FROM "ParkingCache".Parking p
INNER JOIN "CarCache".Car c
  ON (p.id) = (c.parkingId)
GROUP BY P.NAME
{code}
3) Switch results presentation to area charts and configure "Name" or "Row 
index" as X axis and "Num" and "Cnt" as Y axis.
- Initially chart show valid data, but on move cursor chart is rebuilt with 
random data



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request #861: gridgain-7.5.30

[sboikov]

GitHub user sboikov opened a pull request:

https://github.com/apache/ignite/pull/861

gridgain-7.5.30



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite gridgain-7.5.30

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/861.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #861


commit 3def50cecc70ee45be5d71a7b82c41f9e9e484b4
Author: nikolay_tikhonov 
Date:   2016-03-23T11:03:26Z

Fixed tests.

commit aa8dcd11aa311e6dd639e0a25c5b0eb714e663ad
Author: nikolay_tikhonov 
Date:   2016-03-23T12:47:17Z

Fixed Ignite Client Nodes suite.

commit 4cb994a7253c6b493b4a376ed1489513ecefd8f9
Author: nikolay_tikhonov 
Date:   2016-03-25T08:20:39Z

IGNITE-GG-11048 Fix missed event notification in remove-remove case.

commit 31ae7ea791e258c49f1b25944cba75fd08d0ca49
Author: nikolay_tikhonov 
Date:   2016-03-25T09:37:25Z

Removed isDebug from test.

commit 1c04005c08ae7ca2006d6f2f687a95c2638c73fc
Author: nikolay_tikhonov 
Date:   2016-03-25T12:22:37Z

IGNITE-GG-11048 Added tests.

commit 53a87290fe028e12a81058fc4b2f2f2341395f9a
Author: Tikhonov Nikolay 
Date:   2016-03-25T16:49:31Z

Fixed tests (renamed test methods).

commit ce56625099b5253f8baf27bfbcff4682787a5ee1
Author: Anton Vinogradov 
Date:   2016-03-28T11:13:20Z

Query Suite separation : 1,2,3

commit 08f5981509711e65c0d4c6fc1209068f8958eb06
Author: vozerov-gridgain 
Date:   2016-03-28T09:24:16Z

Support optional IO policy resolver in DataStreamer.

commit 60e74618b310dafc28eb5f935859fed4ec87584c
Author: vozerov-gridgain 
Date:   2016-03-28T11:52:13Z

Merge remote-tracking branch 'upstream/gridgain-7.5.10' into gridgain-7.5.10

commit 9e84e508a394b790ef046cdcf2a015bcf853c064
Author: nikolay_tikhonov 
Date:   2016-03-28T13:59:56Z

Divide test suite.

commit d36a2e51e3aa3105dff73839c84e52a531fbd918
Author: Denis Magda 
Date:   2016-03-24T17:07:48Z

IGNITE-2849: BinaryObjectBuilder doesn't properly check metadata

commit 9e62b667e73396d3affbc4d1e62449d07d08ec8b
Author: Anton Vinogradov 
Date:   2016-03-29T11:56:21Z

 IGNITE-2801 Coordinator floods network with partitions full map exchange 
messages

commit 85a675b7bfbc54745ee9ce95d5786b5bae5be963
Author: iveselovskiy 
Date:   2016-01-18T14:28:42Z

IGNITE-1788: Removed duplicate check of a single invariant from 
IgfsProcessor.  This closes #221.

commit 0e753c38a986cbd46eb24845808ec1d0fc7d1dea
Author: dkarachentsev 
Date:   2016-02-10T09:38:43Z

IGNITE-2575: Added validation of IGFS endpoint port value. This closes #469.

commit 99028b509c736b79faac7fb8104b1bc3cfe30720
Author: vozerov-gridgain 
Date:   2016-03-03T09:56:55Z

IGFS: Minor refactoring.

commit 219238f2793a3f3f9f5705a065c67510c286df1c
Author: vozerov-gridgain 
Date:   2016-03-03T10:25:43Z

IGNITE-2754: IGFS: Created separate processor for listing remove operation.

commit ff5b68ca69050817794ef4b142c955a186e03de9
Author: vozerov-gridgain 
Date:   2016-03-14T07:19:23Z

IGNITE-2781: IGFS: Force "copyOnRead=false" for meta and data caches.

commit 37c4d508c9e40dcba274ae1625d7bf59bfeef144
Author: vozerov-gridgain 
Date:   2016-03-14T08:49:03Z

IGNITE-2810: IGFS: Striped trash directory to reduce contention during 
removals.

commit 54e6991cb1d0b68c4490dede603c9e3ba7cc3b9e
Author: vozerov-gridgain 
Date:   2016-03-14T09:05:39Z

IGNITE-2810: IGFS: Minor correction to IgfsUtils.isRootOrTrashId() method.

commit 8083391be726c2bbc27e018983ca713e4b25e2a2
Author: vozerov-gridgain 
Date:   2016-03-14T10:17:58Z

IGNITE-2814: IGFS: File lock/unlock/reserve operations are no longer 
require put/replace on cache. Thin entry processors are used instead.

commit a7c1f44420ae96f183abc2e17125f0c9aa0775d5
Author: vozerov-gridgain 
Date:   2016-03-14T12:57:28Z

IGNITE-2828: IGFS: Introduced processor for "updateTimes" operation.

commit ba30ddbc599d67f398ffba1263d174f5b58b4b7d
Author: thatcoach 
Date:   2016-03-15T17:46:13Z

IGNITE-2838: IGFS: Opimized format of IgfsListingEntry. Now it contains 
only file ID and boolean flag endicating whether this a directory or file.

commit 4f7e3c1c2e82596a26cec3b3587991ae18078b64
Author: vozerov-gridgain 
Date:   2016-03-16T06:14:49Z

IGNITE-2817: IGFS: Optimized "updateProperties" and