Re: Allow distributed SQL query execution over explicit set of partitions

[Vladimir Ozerov]

Several side notes about API.

1) I would avoid ranges even in this form.for the sake of simplicity.
Ignite do not have any notion of "partition range" in affinity API, so I do
not understand how users are going to work on ranges unless they have some
very special custom affinity function, which is rather unlikely case.

2) The fact that this property is ignored in REPLICATED cache is confusing.
REPLICATED cache still divides partitions into primaries and backups. If I
have very large data set and want to execute some query, I would definitely
expect that Ignite will take advantage of distributed computing and spread
the load between nodes. I understand that currently SQL queries do not work
this way, but this is clear disadvantage for certain scenarios, which we
may improve in future. I would remove this paragraph from docs.

3) We already have ScanQuery.partition getter/setter. We need to make sure
that they are "merged" somehow. For instance, we may deprecate two methods
in ScanQuery class, and advise users to use Query.partitions, with
clarification - only single partition is supported for ScanQuery at the
moment.

4) What should happen if "partitions" are defined and "local" flag is set?

As per distributed joins - how are we going to execute them when partitions
are set explicitly? As far as I understand, partitions should apply only to
map step and only for the cache query was created from, This way
distributed join execution should effectively ignore partitions?

Vladimir.


On Thu, Jan 19, 2017 at 1:04 AM, Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:

> I mean distributed joins.
>
> 2017-01-19 0:10 GMT+03:00 Alexei Scherbakov 
> :
>
> > Guys,
> >
> > I've finished adding API changes and implemented proper nodes routing.
> >
> > Currently it doesn't work with distributed queries.But I think this
> > feature should be compatible with it.
> >
> > Could anyone take a look at current branch state while I'm looking deeper
> > into dsitributed queries code?
> >
> > Issue: https://issues.apache.org/jira/browse/IGNITE-4523
> > PR: https://github.com/apache/ignite/pull/1418
> >
> >
> >
> > 2017-01-13 15:55 GMT+03:00 Alexei Scherbakov <
> alexey.scherbak...@gmail.com
> > >:
> >
> >> OK, let's do it this way.
> >>
> >>
> >>
> >>
> >>
> >> 2017-01-13 13:27 GMT+03:00 Sergi Vladykin :
> >>
> >>> Internally we still use int[] when we send partitions (see
> >>> GridH2QueryRequest.parts). It looks like we only do more work with
> >>> PartitionSet.
> >>>
> >>> I like the idea of bitset for partitions, but
> >>>
> >>> 1. We have to change internals first to use it, otherwise the
> >>> optimization
> >>> makes no sense.
> >>> 2. We will need to have a method SqlQuery.setPartitions(int... parts)
> for
> >>> usability reasons anyways.
> >>>
> >>> Thus I suggest for now to go the straightforward way with int[] and
> >>> create
> >>> a separate ticket describing the optimization with bitset.
> >>>
> >>> Sergi
> >>>
> >>> 2017-01-13 13:06 GMT+03:00 Alexei Scherbakov <
> >>> alexey.scherbak...@gmail.com>:
> >>>
> >>> > PartitionSet hides internal implementation of int array.
> >>> >
> >>> > This allows as to efficiently represent contiguous range of
> partitions
> >>> and
> >>> > defines clear API for ordered iteration over partitions and
> containment
> >>> > check.
> >>> >
> >>> > Even better to go with compressed bitmap, as I mentioned in ticket
> >>> comment.
> >>> > This will allow us to minimize heap footprint for this object.
> >>> >
> >>> > Moreover, it will be useful to create reusable compressed bitmap
> >>> > implementation in Ignite and use it in other cases, on example, for
> >>> > replacing H2's IntArray and Set.
> >>> >
> >>> > Should I create a ticket for this ?
> >>> >
> >>> > .
> >>> >
> >>> > 2017-01-13 1:01 GMT+03:00 Dmitriy Setrakyan :
> >>> >
> >>> > > On Thu, Jan 12, 2017 at 6:12 AM, Sergi Vladykin <
> >>> > sergi.vlady...@gmail.com>
> >>> > > wrote:
> >>> > >
> >>> > > > I looked at the code. The PartitionSet concept looks
> >>> overengineered to
> >>> > > me,
> >>> > > > why wouldn't we just go with int[]?
> >>> > > >
> >>> > >
> >>> > > Agree.
> >>> > >
> >>> > >
> >>> > > >
> >>> > > > Sergi
> >>> > > >
> >>> > > > 2017-01-12 15:18 GMT+03:00 Alexei Scherbakov <
> >>> > > alexey.scherbak...@gmail.com
> >>> > > > >:
> >>> > > >
> >>> > > > > Done.
> >>> > > > >
> >>> > > > > 2017-01-11 20:39 GMT+03:00 Dmitriy Setrakyan <
> >>> dsetrak...@apache.org
> >>> > >:
> >>> > > > >
> >>> > > > > > Alexey,
> >>> > > > > >
> >>> > > > > > I am not sure I am seeing the API changes documented in the
> >>> ticket.
> >>> > > Can
> >>> > > > > you
> >>> > > > > > please either document them or add GIT links for the new
> >>> classes?
> >>> > > > > >
> >>> > > > > > D.
> >>> > > > > >
> >>> > > > > > On Wed, Jan 11, 2017 at 9:29 AM, Alexei Scherbakov <
> >>> > > > > > alexey.scherbak...@gmail.com> wrote:
> >>> > > > > >
> >>> 

[jira] [Created] (IGNITE-4561) Improve JdbcTypesTransformer to make mapping more flexible

[Andrey Novikov (JIRA)]

Andrey Novikov created IGNITE-4561:
--

 Summary: Improve JdbcTypesTransformer to make mapping more flexible
 Key: IGNITE-4561
 URL: https://issues.apache.org/jira/browse/IGNITE-4561
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.8
Reporter: Andrey Novikov
Priority: Minor
 Fix For: 2.0


Need move logic with query parameter transformation from: 
org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore#fillParameter to: 
org.apache.ignite.cache.store.jdbc.JdbcTypesTransformer

Need extend JdbcTypesTransformer#getColumnValue by adding information about 
cache, type, field.



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

Re: Partition data lost event

[Alexey Goncharuk]

Val et al,

Currently partition lost event is fired on nodes which should become
partition owners, but did not find other partition owners to rebalance data
from. In your example one of the node should have became an owner for
partitions 1, 3, the other - for partitions 2, 4 (according to the affinity
function assignment), thus this set of events is fired.

In Ignite 2.0 lost partitions will be handled on coordinator and events
will be fired for all partitions on all cache nodes.

--AG

2017-01-18 23:39 GMT+03:00 Denis Magda :

> Alex G. and Yakov should be able to clarify this since they took part in
> the creation of the following tickets related to partitions lost consistency
> https://issues.apache.org/jira/browse/IGNITE-1605 <
> https://issues.apache.org/jira/browse/IGNITE-1605>
> https://issues.apache.org/jira/browse/IGNITE-2378 <
> https://issues.apache.org/jira/browse/IGNITE-2378>
>
> —
> Denis
>
> > On Jan 18, 2017, at 12:16 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
> >
> > Folks,
> >
> > Does anyone know how the EVT_CACHE_REBALANCE_PART_DATA_LOST event is
> fired?
> > I just create a small test and the result confused me. This is what I do:
> >
> > 1. Start several server nodes, all listen to
> > EVT_CACHE_REBALANCE_PART_DATA_LOST event.
> > 2. Create a cache with no backups.
> > 3. Put some values.
> > 4. Stop one of the nodes (lose some partitions).
> >
> > What I noticed is that the event is fired on all nodes that are still in
> > topology, but for different partitions. For example, if there are 4
> > partitions lost (1,2,3,4), I can get notifications for 1,3 on first node
> > and 2,4 on second node. This seems weird and it's not clear to me how to
> > use this event.
> >
> > Can anyone explain this behavior? Is this expected?
> >
> > Here is the test code:
> >
> > public class PartitionTest {
> >public static void main(String[] args) throws InterruptedException {
> >for (int i = 0; i < 4; i++)
> >Ignition.start(config("server-" + i));
> >
> >Ignition.setClientMode(true);
> >
> >Ignite ignite = Ignition.start();
> >
> >CacheConfiguration cfg = new
> > CacheConfiguration<>("test");
> >
> >cfg.setAffinity(new RendezvousAffinityFunction(20, null));
> >
> >IgniteCache cache = ignite.createCache(cfg);
> >
> >for (int i = 0; i < 100; i++)
> >cache.put(i, i);
> >
> >System.out.println("Populated.");
> >
> >Thread.sleep(2000);
> >
> >Ignition.stop("server-3", true);
> >}
> >
> >private static IgniteConfiguration config(String name) {
> >IgniteConfiguration cfg = new IgniteConfiguration();
> >
> >cfg.setGridName(name);
> >
> > cfg.setIncludeEventTypes(EventType.EVT_CACHE_REBALANCE_PART_DATA_LOST);
> >cfg.setLocalEventListeners(Collections. Event>, int[]>singletonMap(
> >new IgnitePredicate() {
> >@Override public boolean apply(Event event) {
> >U.debug("EVENT: " + event);
> >
> >return true;
> >}
> >},
> >new int[] {EventType.EVT_CACHE_REBALANCE_PART_DATA_LOST}
> >));
> >
> >return cfg;
> >}
> > }
> >
> > -Val
>
>

Re: Hibernate OGM for Ignite. I need a help with documentation

[Prachi Garg]

Hi Victor,

I have tried to fix the document. However, I do have some questions. Please
see my comments in the document.

https://docs.google.com/document/d/1ZSFt9NPnN8EyOpNnNguc5-9FIDr4RfQLfAZMH0VgBPc/edit#

Thanks,
-Prachi

On Tue, Jan 17, 2017 at 7:22 PM, Denis Magda  wrote:

> Hi Victor,
>
> This seems to be a duplicate message. Please join the conversation in the
> original message
> http://apache-ignite-developers.2346864.n4.nabble.
> com/Hibernate-OGM-for-Ignite-I-need-a-help-with-documentation-tp13762.html
>  com/Hibernate-OGM-for-Ignite-I-need-a-help-with-documentation-tp13762.html
> >
>
> —
> Denis
>
> > On Jan 17, 2017, at 12:12 PM, Victor Z  wrote:
> >
> > Hi everybody!
> >
> > Hibernate OGM  is a JPA implementation for
> NoSQL
> > datastores. I'm creating module for Apache Ignite.
> > Here is my work
> > ,
> and pull
> > request  ApacheIgnite>
> > to Hibernate OGM
> > I've almost done, but there is one issue with documentation. I have to
> > write it.
> > But I'm programmer, not a techwriter, and my English is not very good.
> > I made a draft of documentation
> > https://drive.google.com/open?id=0B2da3AGK_cO6TWpvVzFrWWF0dEk
> >
> > Could you please take a look at this to correct mistakes or to add some
> > useful information?
> >
> > Here is existing documentation
> >  that I
> > used as an example.
> >
> > Thank you in advance,
> > Victor
>
>

Blogs updates: 1.8 release, Redis, Microservices and more

[Denis Magda]

Community,

Some of us published new blog posts this month. Please go ahead and enjoy:
https://ignite.apache.org/blogs.html 

—
Denis

[GitHub] ignite pull request #1441: IGNITE-3537

[javaller]

GitHub user javaller reopened a pull request:

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

IGNITE-3537

Added tests for IgniteSet, IgniteQueue, IgniteSemaphore, IgniteLock, 
IgniteCountDownLatch, IgniteAtomicStamped, IgniteAtomicReference, 
IgniteAtomicLong.
Added new testcases ( testIsolation method ) into classes  
GridCacheSetAbstractSelfTest, GridCacheQueueApiSelfAbstractTest, 
IgniteSemaphoreAbstractSelfTest, IgniteLockAbstractSelfTest, 
IgniteCountDownLatchAbstractSelfTest, 
GridCacheAtomicStampedApiSelfAbstractTest, 
GridCacheAtomicReferenceApiSelfAbstractTest, 
IgniteAtomicLongApiAbstractSelfTest.

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

$ git pull https://github.com/javaller/ignite master

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

https://github.com/apache/ignite/pull/1441.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 #1441


commit e41a92f051594953f5f67c86e3c2878dfbb2e4e2
Author: javaller 
Date:   2016-12-15T14:27:01Z

test commit & push

commit 9f204b1d9d2cd3a12e1cbe0c487b42da96963a78
Author: javaller 
Date:   2016-12-18T14:38:37Z

Added tests for IgniteSet, IgniteQueue, IgniteSemaphore, IgniteLock, 
IgniteCountDownLatch, IgniteAtomicStamped, IgniteAtomicReference, 
IgniteAtomicLong.
Added new testcases ( testIsolation methon ) into classes  
GridCacheSetAbstractSelfTest, GridCacheQueueApiSelfAbstractTest, 
IgniteSemaphoreAbstractSelfTest, IgniteLockAbstractSelfTest, 
IgniteCountDownLatchAbstractSelfTest, 
GridCacheAtomicStampedApiSelfAbstractTest, 
GridCacheAtomicReferenceApiSelfAbstractTest, 
IgniteAtomicLongApiAbstractSelfTest.

commit 6b74e31b73db61b04c9bbd7dc99297049c39d81f
Author: javaller 
Date:   2016-12-18T18:47:58Z

IGNITE-3537:
Added tests for IgniteSet, IgniteQueue, IgniteSemaphore, IgniteLock, 
IgniteCountDownLatch, IgniteAtomicStamped, IgniteAtomicReference, 
IgniteAtomicLong.
Added new testcases ( testIsolation method ) into classes  
GridCacheSetAbstractSelfTest, GridCacheQueueApiSelfAbstractTest, 
IgniteSemaphoreAbstractSelfTest, IgniteLockAbstractSelfTest, 
IgniteCountDownLatchAbstractSelfTest, 
GridCacheAtomicStampedApiSelfAbstractTest, 
GridCacheAtomicReferenceApiSelfAbstractTest, 
IgniteAtomicLongApiAbstractSelfTest.

commit 29311621a121ab280176ccfef12704d0a84f8601
Author: javaller 
Date:   2016-12-18T18:48:53Z

Merge remote-tracking branch 'origin/master'




---
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.
---

[GitHub] ignite pull request #1441: IGNITE-3537

[javaller]

GitHub user javaller opened a pull request:

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

IGNITE-3537

Added tests for IgniteSet, IgniteQueue, IgniteSemaphore, IgniteLock, 
IgniteCountDownLatch, IgniteAtomicStamped, IgniteAtomicReference, 
IgniteAtomicLong.
Added new testcases ( testIsolation method ) into classes  
GridCacheSetAbstractSelfTest, GridCacheQueueApiSelfAbstractTest, 
IgniteSemaphoreAbstractSelfTest, IgniteLockAbstractSelfTest, 
IgniteCountDownLatchAbstractSelfTest, 
GridCacheAtomicStampedApiSelfAbstractTest, 
GridCacheAtomicReferenceApiSelfAbstractTest, 
IgniteAtomicLongApiAbstractSelfTest.

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

$ git pull https://github.com/javaller/ignite master

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

https://github.com/apache/ignite/pull/1441.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 #1441


commit e41a92f051594953f5f67c86e3c2878dfbb2e4e2
Author: javaller 
Date:   2016-12-15T14:27:01Z

test commit & push

commit 9f204b1d9d2cd3a12e1cbe0c487b42da96963a78
Author: javaller 
Date:   2016-12-18T14:38:37Z

Added tests for IgniteSet, IgniteQueue, IgniteSemaphore, IgniteLock, 
IgniteCountDownLatch, IgniteAtomicStamped, IgniteAtomicReference, 
IgniteAtomicLong.
Added new testcases ( testIsolation methon ) into classes  
GridCacheSetAbstractSelfTest, GridCacheQueueApiSelfAbstractTest, 
IgniteSemaphoreAbstractSelfTest, IgniteLockAbstractSelfTest, 
IgniteCountDownLatchAbstractSelfTest, 
GridCacheAtomicStampedApiSelfAbstractTest, 
GridCacheAtomicReferenceApiSelfAbstractTest, 
IgniteAtomicLongApiAbstractSelfTest.

commit 6b74e31b73db61b04c9bbd7dc99297049c39d81f
Author: javaller 
Date:   2016-12-18T18:47:58Z

IGNITE-3537:
Added tests for IgniteSet, IgniteQueue, IgniteSemaphore, IgniteLock, 
IgniteCountDownLatch, IgniteAtomicStamped, IgniteAtomicReference, 
IgniteAtomicLong.
Added new testcases ( testIsolation method ) into classes  
GridCacheSetAbstractSelfTest, GridCacheQueueApiSelfAbstractTest, 
IgniteSemaphoreAbstractSelfTest, IgniteLockAbstractSelfTest, 
IgniteCountDownLatchAbstractSelfTest, 
GridCacheAtomicStampedApiSelfAbstractTest, 
GridCacheAtomicReferenceApiSelfAbstractTest, 
IgniteAtomicLongApiAbstractSelfTest.

commit 29311621a121ab280176ccfef12704d0a84f8601
Author: javaller 
Date:   2016-12-18T18:48:53Z

Merge remote-tracking branch 'origin/master'




---
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: Allow distributed SQL query execution over explicit set of partitions

[Alexei Scherbakov]

I mean distributed joins.

2017-01-19 0:10 GMT+03:00 Alexei Scherbakov :

> Guys,
>
> I've finished adding API changes and implemented proper nodes routing.
>
> Currently it doesn't work with distributed queries.But I think this
> feature should be compatible with it.
>
> Could anyone take a look at current branch state while I'm looking deeper
> into dsitributed queries code?
>
> Issue: https://issues.apache.org/jira/browse/IGNITE-4523
> PR: https://github.com/apache/ignite/pull/1418
>
>
>
> 2017-01-13 15:55 GMT+03:00 Alexei Scherbakov  >:
>
>> OK, let's do it this way.
>>
>>
>>
>>
>>
>> 2017-01-13 13:27 GMT+03:00 Sergi Vladykin :
>>
>>> Internally we still use int[] when we send partitions (see
>>> GridH2QueryRequest.parts). It looks like we only do more work with
>>> PartitionSet.
>>>
>>> I like the idea of bitset for partitions, but
>>>
>>> 1. We have to change internals first to use it, otherwise the
>>> optimization
>>> makes no sense.
>>> 2. We will need to have a method SqlQuery.setPartitions(int... parts) for
>>> usability reasons anyways.
>>>
>>> Thus I suggest for now to go the straightforward way with int[] and
>>> create
>>> a separate ticket describing the optimization with bitset.
>>>
>>> Sergi
>>>
>>> 2017-01-13 13:06 GMT+03:00 Alexei Scherbakov <
>>> alexey.scherbak...@gmail.com>:
>>>
>>> > PartitionSet hides internal implementation of int array.
>>> >
>>> > This allows as to efficiently represent contiguous range of partitions
>>> and
>>> > defines clear API for ordered iteration over partitions and containment
>>> > check.
>>> >
>>> > Even better to go with compressed bitmap, as I mentioned in ticket
>>> comment.
>>> > This will allow us to minimize heap footprint for this object.
>>> >
>>> > Moreover, it will be useful to create reusable compressed bitmap
>>> > implementation in Ignite and use it in other cases, on example, for
>>> > replacing H2's IntArray and Set.
>>> >
>>> > Should I create a ticket for this ?
>>> >
>>> > .
>>> >
>>> > 2017-01-13 1:01 GMT+03:00 Dmitriy Setrakyan :
>>> >
>>> > > On Thu, Jan 12, 2017 at 6:12 AM, Sergi Vladykin <
>>> > sergi.vlady...@gmail.com>
>>> > > wrote:
>>> > >
>>> > > > I looked at the code. The PartitionSet concept looks
>>> overengineered to
>>> > > me,
>>> > > > why wouldn't we just go with int[]?
>>> > > >
>>> > >
>>> > > Agree.
>>> > >
>>> > >
>>> > > >
>>> > > > Sergi
>>> > > >
>>> > > > 2017-01-12 15:18 GMT+03:00 Alexei Scherbakov <
>>> > > alexey.scherbak...@gmail.com
>>> > > > >:
>>> > > >
>>> > > > > Done.
>>> > > > >
>>> > > > > 2017-01-11 20:39 GMT+03:00 Dmitriy Setrakyan <
>>> dsetrak...@apache.org
>>> > >:
>>> > > > >
>>> > > > > > Alexey,
>>> > > > > >
>>> > > > > > I am not sure I am seeing the API changes documented in the
>>> ticket.
>>> > > Can
>>> > > > > you
>>> > > > > > please either document them or add GIT links for the new
>>> classes?
>>> > > > > >
>>> > > > > > D.
>>> > > > > >
>>> > > > > > On Wed, Jan 11, 2017 at 9:29 AM, Alexei Scherbakov <
>>> > > > > > alexey.scherbak...@gmail.com> wrote:
>>> > > > > >
>>> > > > > > > Guys,
>>> > > > > > >
>>> > > > > > > I've just submitted a PR for
>>> > > > > > > https://issues.apache.org/jira/browse/IGNITE-4523.
>>> > > > > > >
>>> > > > > > > Please review API changes while waiting for TC results.
>>> > > > > > >
>>> > > > > > > --
>>> > > > > > >
>>> > > > > > > Best regards,
>>> > > > > > > Alexei Scherbakov
>>> > > > > > >
>>> > > > > >
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > > > --
>>> > > > >
>>> > > > > Best regards,
>>> > > > > Alexei Scherbakov
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> > Best regards,
>>> > Alexei Scherbakov
>>> >
>>>
>>
>>
>>
>> --
>>
>> Best regards,
>> Alexei Scherbakov
>>
>
>
>
> --
>
> Best regards,
> Alexei Scherbakov
>



-- 

Best regards,
Alexei Scherbakov

Re: Allow distributed SQL query execution over explicit set of partitions

[Alexei Scherbakov]

Guys,

I've finished adding API changes and implemented proper nodes routing.

Currently it doesn't work with distributed queries.But I think this feature
should be compatible with it.

Could anyone take a look at current branch state while I'm looking deeper
into dsitributed queries code?

Issue: https://issues.apache.org/jira/browse/IGNITE-4523
PR: https://github.com/apache/ignite/pull/1418



2017-01-13 15:55 GMT+03:00 Alexei Scherbakov :

> OK, let's do it this way.
>
>
>
>
>
> 2017-01-13 13:27 GMT+03:00 Sergi Vladykin :
>
>> Internally we still use int[] when we send partitions (see
>> GridH2QueryRequest.parts). It looks like we only do more work with
>> PartitionSet.
>>
>> I like the idea of bitset for partitions, but
>>
>> 1. We have to change internals first to use it, otherwise the optimization
>> makes no sense.
>> 2. We will need to have a method SqlQuery.setPartitions(int... parts) for
>> usability reasons anyways.
>>
>> Thus I suggest for now to go the straightforward way with int[] and create
>> a separate ticket describing the optimization with bitset.
>>
>> Sergi
>>
>> 2017-01-13 13:06 GMT+03:00 Alexei Scherbakov <
>> alexey.scherbak...@gmail.com>:
>>
>> > PartitionSet hides internal implementation of int array.
>> >
>> > This allows as to efficiently represent contiguous range of partitions
>> and
>> > defines clear API for ordered iteration over partitions and containment
>> > check.
>> >
>> > Even better to go with compressed bitmap, as I mentioned in ticket
>> comment.
>> > This will allow us to minimize heap footprint for this object.
>> >
>> > Moreover, it will be useful to create reusable compressed bitmap
>> > implementation in Ignite and use it in other cases, on example, for
>> > replacing H2's IntArray and Set.
>> >
>> > Should I create a ticket for this ?
>> >
>> > .
>> >
>> > 2017-01-13 1:01 GMT+03:00 Dmitriy Setrakyan :
>> >
>> > > On Thu, Jan 12, 2017 at 6:12 AM, Sergi Vladykin <
>> > sergi.vlady...@gmail.com>
>> > > wrote:
>> > >
>> > > > I looked at the code. The PartitionSet concept looks overengineered
>> to
>> > > me,
>> > > > why wouldn't we just go with int[]?
>> > > >
>> > >
>> > > Agree.
>> > >
>> > >
>> > > >
>> > > > Sergi
>> > > >
>> > > > 2017-01-12 15:18 GMT+03:00 Alexei Scherbakov <
>> > > alexey.scherbak...@gmail.com
>> > > > >:
>> > > >
>> > > > > Done.
>> > > > >
>> > > > > 2017-01-11 20:39 GMT+03:00 Dmitriy Setrakyan <
>> dsetrak...@apache.org
>> > >:
>> > > > >
>> > > > > > Alexey,
>> > > > > >
>> > > > > > I am not sure I am seeing the API changes documented in the
>> ticket.
>> > > Can
>> > > > > you
>> > > > > > please either document them or add GIT links for the new
>> classes?
>> > > > > >
>> > > > > > D.
>> > > > > >
>> > > > > > On Wed, Jan 11, 2017 at 9:29 AM, Alexei Scherbakov <
>> > > > > > alexey.scherbak...@gmail.com> wrote:
>> > > > > >
>> > > > > > > Guys,
>> > > > > > >
>> > > > > > > I've just submitted a PR for
>> > > > > > > https://issues.apache.org/jira/browse/IGNITE-4523.
>> > > > > > >
>> > > > > > > Please review API changes while waiting for TC results.
>> > > > > > >
>> > > > > > > --
>> > > > > > >
>> > > > > > > Best regards,
>> > > > > > > Alexei Scherbakov
>> > > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > >
>> > > > > Best regards,
>> > > > > Alexei Scherbakov
>> > > > >
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> >
>> > Best regards,
>> > Alexei Scherbakov
>> >
>>
>
>
>
> --
>
> Best regards,
> Alexei Scherbakov
>



-- 

Best regards,
Alexei Scherbakov

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

[Sally Khudairi]

You're most welcome, Denis. It's my pleasure.
Of course you may include the post in your blog. Feel free to use the Apache 
feather for the image :^)
Cheers,Sally


[From the mobile; please excuse top-posting, spelling/spacing errors, and 
brevity]


 
 
  On Wed, Jan 18, 2017 at 15:55, Denis Magda wrote:   Sally, 
this is amazing! Thanks for all your hard work you did helping the community to 
share the news widely!
Could we add this blog post to our page?https://ignite.apache.org/blogs.html
If yes, please share the photo you want us to use for your account.
—Denis

On Jan 18, 2017, at 2:18 AM, Sally Khudairi  wrote:
Hello everyone --as promised, we are live:
 - ASF "Foundation" blog https://s.apache.org/Slah
 - @TheASF Twitter feed https://twitter.com/TheASF/status/821660992522297344
 - NEW! ASF LinkedIn page 
https://www.linkedin.com/company/the-apache-software-foundation
... as well as to announce@ and our dedicated media/analyst list. This will 
appear on the apache.org homepage and archives during the next auto-update, 
which should take place within the hour.
Thanks again for all your help and a job well done!
Warmly,
Sally = = = = =  vox +1 617 921 8656gvox +1 646 598 4616skype sallykhudairi

  From: Sally Khudairi 
 To: Denis Magda ; Sally Khudairi  
Cc: "dev@ignite.apache.org" 
 Sent: Tuesday, January 17, 2017 1:52 PM
 Subject: Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

OK great; thanks, Denis!
I've accepted almost all suggestions, except for the ones that align with ASF 
editorial house style (= "look" vs. meaning).
Kind thanks,Sally


[From the mobile; please excuse top-posting, spelling/spacing errors, and 
brevity]




 On Tue, Jan 17, 2017 at 13:41, Denis Magda wrote:  Hi Sally,
I’ve finished on my side. Please see my suggestions in the google doc.
If anyone else is willing to review the announcement please do it by 18.00 PM 
EST (15.00 PST).
—Denis

On Jan 17, 2017, at 9:20 AM, Sally Khudairi  wrote:
Hi everyone --just confirming that we'll need to lock in the copy in ~6 hours 
in order to announce tomorrow morning.
Denis, if you can please forward the copy when ready so the PMC has a chance to 
review in time, that would be great.
Thanks so much,
Sally = = = = =  vox +1 617 921 8656gvox +1 646 598 4616skype sallykhudairi

  From: Sally Khudairi 
 To: Denis Magda ; "s...@apache.org"  
Cc: "dev@ignite.apache.org" 
 Sent: Sunday, January 15, 2017 9:20 AM
 Subject: Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

Excellent. Thank you, Denis.
Enjoy the day!
-Sally


[From the mobile; please excuse top-posting, spelling/spacing errors, and 
brevity]




 On Sun, Jan 15, 2017 at 9:12, Denis Magda wrote:  Thanks, 
Sally. Confirm that I could access and edit the doc. 
Sure, I’ll finish the editing by that time. Most likely this will be the first 
thing to do on Tuesday.
—Denis

On Jan 15, 2017, at 3:07 AM, Sally Khudairi  wrote:
Oh wow --Denis, thank you!
I must say, the documentation on Ignite is exhaustive and comprehensive, so 
pulling things together was an "embarrassment of riches" experience . Gold 
Star to the PMC --I'll definitely use this as an example for other projects to 
emulate.

OK...I just sent you editing credentials, and look forward to locking in the 
copy hopefully by 6PM ET on Tuesday so we can go live Wednesday morning.
Does that work for you?
Kind thanks again,Sally

[From the mobile; please excuse top-posting, spelling/spacing errors, and 
brevity]




 On Sat, Jan 14, 2017 at 23:38, Denis Magda wrote:  Sally, 
You understood everything perfectly well producing such a clear and great 
article! Not sure that anyone could write better ;)
Please give editing permissions to my google account (magda7...@gmail.com). 
I’ll fill in the missing part.
—Denis

On Jan 14, 2017, at 9:01 AM, Sally Khudairi  wrote:
Hello, everyone --as promised, below is the draft so far. Here's hoping I 
understood everything correctly 
Kindly note that we'll need to fill in the "@@" under the hood section on v1.8 
(this part can be technical and developer-focused, whilst the rest of the 
document should be tech-lite = understandable for journalists who are geeky but 
not technologists). I'll be happy to provide editing credentials on the 
googledoc to those requesting it.
Do keep in mind that this is not a press release, so the format is different 
from what we're used to (I launched the "Have you met...?" series with 
Mahout[1] back in 2010 to great media interest: coverage within 24 hours). We 
can also work together on establishing a template for you to use for future 
project announcements.
As always, comments/corrections/additions welcome!
Thanks so much,Sally
[1] 
= = =
The ASF asks: Have you met 

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

[Denis Magda]

Sally, this is amazing! Thanks for all your hard work you did helping the 
community to share the news widely!

Could we add this blog post to our page?
https://ignite.apache.org/blogs.html 

If yes, please share the photo you want us to use for your account.

—
Denis

> On Jan 18, 2017, at 2:18 AM, Sally Khudairi  wrote:
> 
> Hello everyone --as promised, we are live:
>  - ASF "Foundation" blog https://s.apache.org/Slah
>  - @TheASF Twitter feed https://twitter.com/TheASF/status/821660992522297344
>  - NEW! ASF LinkedIn page 
> https://www.linkedin.com/company/the-apache-software-foundation
> ... as well as to announce@ and our dedicated media/analyst list. This will 
> appear on the apache.org homepage and archives during the next auto-update, 
> which should take place within the hour.
> Thanks again for all your help and a job well done!
> Warmly,
> Sally = = = = =  vox +1 617 921 8656gvox +1 646 598 4616skype sallykhudairi
> 
>  From: Sally Khudairi 
> To: Denis Magda ; Sally Khudairi  
> Cc: "dev@ignite.apache.org" 
> Sent: Tuesday, January 17, 2017 1:52 PM
> Subject: Re: [ANNOUNCE] Apache Ignite 1.8.0 Released
> 
> OK great; thanks, Denis!
> I've accepted almost all suggestions, except for the ones that align with ASF 
> editorial house style (= "look" vs. meaning).
> Kind thanks,Sally
> 
> 
> [From the mobile; please excuse top-posting, spelling/spacing errors, and 
> brevity]
> 
> 
> 
> 
> On Tue, Jan 17, 2017 at 13:41, Denis Magda wrote:  Hi 
> Sally,
> I’ve finished on my side. Please see my suggestions in the google doc.
> If anyone else is willing to review the announcement please do it by 18.00 PM 
> EST (15.00 PST).
> —Denis
> 
> On Jan 17, 2017, at 9:20 AM, Sally Khudairi  wrote:
> Hi everyone --just confirming that we'll need to lock in the copy in ~6 hours 
> in order to announce tomorrow morning.
> Denis, if you can please forward the copy when ready so the PMC has a chance 
> to review in time, that would be great.
> Thanks so much,
> Sally = = = = =  vox +1 617 921 8656gvox +1 646 598 4616skype sallykhudairi
> 
>  From: Sally Khudairi 
> To: Denis Magda ; "s...@apache.org"  
> Cc: "dev@ignite.apache.org" 
> Sent: Sunday, January 15, 2017 9:20 AM
> Subject: Re: [ANNOUNCE] Apache Ignite 1.8.0 Released
> 
> Excellent. Thank you, Denis.
> Enjoy the day!
> -Sally
> 
> 
> [From the mobile; please excuse top-posting, spelling/spacing errors, and 
> brevity]
> 
> 
> 
> 
> On Sun, Jan 15, 2017 at 9:12, Denis Magda wrote:  Thanks, 
> Sally. Confirm that I could access and edit the doc. 
> Sure, I’ll finish the editing by that time. Most likely this will be the 
> first thing to do on Tuesday.
> —Denis
> 
> On Jan 15, 2017, at 3:07 AM, Sally Khudairi  wrote:
> Oh wow --Denis, thank you!
> I must say, the documentation on Ignite is exhaustive and comprehensive, so 
> pulling things together was an "embarrassment of riches" experience . Gold 
> Star to the PMC --I'll definitely use this as an example for other projects 
> to emulate.
> 
> OK...I just sent you editing credentials, and look forward to locking in the 
> copy hopefully by 6PM ET on Tuesday so we can go live Wednesday morning.
> Does that work for you?
> Kind thanks again,Sally
> 
> [From the mobile; please excuse top-posting, spelling/spacing errors, and 
> brevity]
> 
> 
> 
> 
> On Sat, Jan 14, 2017 at 23:38, Denis Magda wrote:  Sally, 
> You understood everything perfectly well producing such a clear and great 
> article! Not sure that anyone could write better ;)
> Please give editing permissions to my google account (magda7...@gmail.com). 
> I’ll fill in the missing part.
> —Denis
> 
> On Jan 14, 2017, at 9:01 AM, Sally Khudairi  wrote:
> Hello, everyone --as promised, below is the draft so far. Here's hoping I 
> understood everything correctly 
> Kindly note that we'll need to fill in the "@@" under the hood section on 
> v1.8 (this part can be technical and developer-focused, whilst the rest of 
> the document should be tech-lite = understandable for journalists who are 
> geeky but not technologists). I'll be happy to provide editing credentials on 
> the googledoc to those requesting it.
> Do keep in mind that this is not a press release, so the format is different 
> from what we're used to (I launched the "Have you met...?" series with 
> Mahout[1] back in 2010 to great media interest: coverage within 24 hours). We 
> can also work together on establishing a template for you to use for future 
> project announcements.
> As always, comments/corrections/additions welcome!
> Thanks so much,Sally
> [1] 
> = = =
> The ASF asks: Have you met Apache Ignite?
> Since 1999, The Apache Software Foundation (ASF) has 

Aleksandr Menshikov: new contributor

[Denis Magda]

Community,

Please welcome a new Apache Ignite contributor, Aleksandr Menshikov, who has 
just finished contribution of the following
https://issues.apache.org/jira/browse/IGNITE-4487 


Alexandr, you were added to official contributors’ list:
https://ignite.apache.org/community/resources.html#people 


Look forward to more contributions from your side!

—
Denis

Re: Partition data lost event

[Denis Magda]

Alex G. and Yakov should be able to clarify this since they took part in the 
creation of the following tickets related to partitions lost consistency
https://issues.apache.org/jira/browse/IGNITE-1605 

https://issues.apache.org/jira/browse/IGNITE-2378 


—
Denis

> On Jan 18, 2017, at 12:16 PM, Valentin Kulichenko 
>  wrote:
> 
> Folks,
> 
> Does anyone know how the EVT_CACHE_REBALANCE_PART_DATA_LOST event is fired?
> I just create a small test and the result confused me. This is what I do:
> 
> 1. Start several server nodes, all listen to
> EVT_CACHE_REBALANCE_PART_DATA_LOST event.
> 2. Create a cache with no backups.
> 3. Put some values.
> 4. Stop one of the nodes (lose some partitions).
> 
> What I noticed is that the event is fired on all nodes that are still in
> topology, but for different partitions. For example, if there are 4
> partitions lost (1,2,3,4), I can get notifications for 1,3 on first node
> and 2,4 on second node. This seems weird and it's not clear to me how to
> use this event.
> 
> Can anyone explain this behavior? Is this expected?
> 
> Here is the test code:
> 
> public class PartitionTest {
>public static void main(String[] args) throws InterruptedException {
>for (int i = 0; i < 4; i++)
>Ignition.start(config("server-" + i));
> 
>Ignition.setClientMode(true);
> 
>Ignite ignite = Ignition.start();
> 
>CacheConfiguration cfg = new
> CacheConfiguration<>("test");
> 
>cfg.setAffinity(new RendezvousAffinityFunction(20, null));
> 
>IgniteCache cache = ignite.createCache(cfg);
> 
>for (int i = 0; i < 100; i++)
>cache.put(i, i);
> 
>System.out.println("Populated.");
> 
>Thread.sleep(2000);
> 
>Ignition.stop("server-3", true);
>}
> 
>private static IgniteConfiguration config(String name) {
>IgniteConfiguration cfg = new IgniteConfiguration();
> 
>cfg.setGridName(name);
> 
> cfg.setIncludeEventTypes(EventType.EVT_CACHE_REBALANCE_PART_DATA_LOST);
>cfg.setLocalEventListeners(Collections., int[]>singletonMap(
>new IgnitePredicate() {
>@Override public boolean apply(Event event) {
>U.debug("EVENT: " + event);
> 
>return true;
>}
>},
>new int[] {EventType.EVT_CACHE_REBALANCE_PART_DATA_LOST}
>));
> 
>return cfg;
>}
> }
> 
> -Val

Partition data lost event

[Valentin Kulichenko]

Folks,

Does anyone know how the EVT_CACHE_REBALANCE_PART_DATA_LOST event is fired?
I just create a small test and the result confused me. This is what I do:

1. Start several server nodes, all listen to
EVT_CACHE_REBALANCE_PART_DATA_LOST event.
2. Create a cache with no backups.
3. Put some values.
4. Stop one of the nodes (lose some partitions).

What I noticed is that the event is fired on all nodes that are still in
topology, but for different partitions. For example, if there are 4
partitions lost (1,2,3,4), I can get notifications for 1,3 on first node
and 2,4 on second node. This seems weird and it's not clear to me how to
use this event.

Can anyone explain this behavior? Is this expected?

Here is the test code:

public class PartitionTest {
public static void main(String[] args) throws InterruptedException {
for (int i = 0; i < 4; i++)
Ignition.start(config("server-" + i));

Ignition.setClientMode(true);

Ignite ignite = Ignition.start();

CacheConfiguration cfg = new
CacheConfiguration<>("test");

cfg.setAffinity(new RendezvousAffinityFunction(20, null));

IgniteCache cache = ignite.createCache(cfg);

for (int i = 0; i < 100; i++)
cache.put(i, i);

System.out.println("Populated.");

Thread.sleep(2000);

Ignition.stop("server-3", true);
}

private static IgniteConfiguration config(String name) {
IgniteConfiguration cfg = new IgniteConfiguration();

cfg.setGridName(name);

cfg.setIncludeEventTypes(EventType.EVT_CACHE_REBALANCE_PART_DATA_LOST);
cfg.setLocalEventListeners(Collections.singletonMap(
new IgnitePredicate() {
@Override public boolean apply(Event event) {
U.debug("EVENT: " + event);

return true;
}
},
new int[] {EventType.EVT_CACHE_REBALANCE_PART_DATA_LOST}
));

return cfg;
}
}

-Val

Aliaksandr Kazlou: new contributor

[Denis Magda]

Community,

Please welcome a new Apache Ignite contributor, Aliaksandr Kazlou, who has just 
joined our team by successfully completing the following task:
Passing AWSCredentialsProvider to TcpDiscoveryS3IpFinder 


Aliaksandr, you were added to official contributors’ list:
https://ignite.apache.org/community/resources.html#people 


Hope that you will be promoted to committers going forward ;)

—
Denis

Re: scripting languages base cases using swig

[Denis Magda]

Sounds interesting. If SWIG does its job really well than agree it worth 
communities efforts to give it a try.

As a side note, I assume that somewhere in the future we will come to the point 
when Ignite will have its own Machine Learning API. For every ML lib it’s 
essential to support Python and R languages that are used by analysts, 
scientists and researches who train models and adjust algorithms before 
everything is deployed in production using Java or C++.

If SWIG can generate Ignite’s APIs for Python and R then it would be a big 
breakthrough for us because the platform will provide all required languages 
needed to adopt an ML lib among researchers and developers.

Could you take in charge of design and create respective JIRA tickets?

—
Denis

> On Jan 17, 2017, at 11:55 PM, Evgeniy Stanilovskiy 
>  wrote:
> 
> Hi Denis,
> 
> I don`t see any problem here, i have to speak with @vozerov about this issue 
> and he recommends me to write it into dev list. All problems that i have with 
> swig is :
> 1. jni overhead (no miracle here ...)
> 2. light troubles with collections API wrapping, like std::map, std::list and 
> so on.
> 
> Partially my open source FreeLing java wrapper you can see here
> https://github.com/TALP-UPC/FreeLing/tree/master/APIs/java
> 
> std_list.i - little stub :) i have talking about.
> 
>> Hi Evgeniy,
>> 
>> Presently we’re trying to fill this gap offering SQL Grid [1]. In a 
>> nutshell, you can connect to an Ignite cluster from your favorite language 
>> or tool with ODBC/JDBC drivers and work with the cluster using SQL SELECT, 
>> INSERT, UPDATE, DELETE statements.
>> 
>> Here is how everything works for PHP that is not natively supported by 
>> Ignite:
>> https://dzone.com/articles/apache-ignite-enables-full-fledged-sql-support-for
>> 
>> However, as for SWIG. Do you think it’s feasible to implement on top of 
>> Ignite.C++ client which is tightly coupled with JVM?
>> 
>> [1] https://apacheignite.readme.io/docs/sql-grid 
>> 
>> 
>> —
>> Denis
>> 
>>> On Jan 16, 2017, at 11:46 PM, Evgeniy Stanilovskiy 
>>>  wrote:
>>> 
>>> Hi all.
>>> Not so long ago i had to know that ignite had reduced functionality support 
>>> in scripting languages.
>>> So, idea was to take an existing C++ client and using SWIG 
>>> (http://www.swig.org) as automatic wrapper, generate clients for absence 
>>> scripting languages.
>>> What do you think about this case ?
>>> 
>>> Thanks !

[GitHub] ignite pull request #1410: ignite-4499

[agura]

Github user agura closed the pull request at:

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


---
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.
---

ApacheCon CFP closing soon (11 February)

[Rich Bowen]

Hello, fellow Apache enthusiast. Thanks for your participation, and
interest in, the projects of the Apache Software Foundation.

I wanted to remind you that the Call For Papers (CFP) for ApacheCon
North America, and Apache: Big Data North America, closes in less than a
month. If you've been putting it off because there was lots of time
left, it's time to dig for that inspiration and get those talk proposals in.

It's also time to discuss with your developer and user community whether
there's a track of talks that you might want to propose, so that you
have more complete coverage of your project than a talk or two.

We're looking for talks directly, and indirectly, related to projects at
the Apache Software Foundation. These can be anything from in-depth
technical discussions of the projects you work with, to talks about
community, documentation, legal issues, marketing, and so on. We're also
very interested in talks about projects and services built on top of
Apache projects, and case studies of how you use Apache projects to
solve real-world problems.

We are particularly interested in presentations from Apache projects
either in the Incubator, or recently graduated. ApacheCon is where
people come to find out what technology they'll be using this time next
year.

Important URLs are:

To submit a talk for Apache: Big Data -
http://events.linuxfoundation.org/events/apache-big-data-north-america/program/cfp
To submit a talk for ApacheCon -
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp

To register for Apache: Big Data -
http://events.linuxfoundation.org/events/apache-big-data-north-america/attend/register-
To register for ApacheCon -
http://events.linuxfoundation.org/events/apachecon-north-america/attend/register-

Early Bird registration rates end March 12th, but if you're a committer
on an Apache project, you get the low committer rate, which is less than
half of the early bird rate!

For further updated about ApacheCon, follow us on Twitter, @ApacheCon,
or drop by our IRC channel, #apachecon on the Freenode IRC network. Or
contact me - rbo...@apache.org - with any questions or concerns.

Thanks!

Rich Bowen, VP Conferences, Apache Software Foundation

-- 
(You've received this email because you're on a dev@ or users@ mailing
list of an Apache Software Foundation project. For subscription and
unsubscription information, consult the headers of this email message,
as this varies from one list to another.)

[GitHub] ignite pull request #1440: Ignite 3699 2

[avinogradovgg]

GitHub user avinogradovgg opened a pull request:

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

Ignite 3699 2



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

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

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

https://github.com/apache/ignite/pull/1440.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 #1440


commit 5ffb8a74d08d998f8258770669ecb240db41964f
Author: sboikov 
Date:   2016-11-22T11:39:14Z

Merge remote-tracking branch 'remotes/community/ignite-1.7.4'

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

commit 9d82f2ca06fa6069c1976cc75814874256b24f8c
Author: devozerov 
Date:   2016-11-22T12:05:29Z

IGNITE-4259: Fixed a problem with geospatial indexes and BinaryMarshaller.

commit e91c15073eb0f9677c8a358a21497e7a6956200f
Author: Pavel Tupitsyn 
Date:   2016-11-22T12:57:52Z

IGNITE-4261 .NET: Fix ScanQuery tests: revert some changes from 
6578c8b1e2dc57861da7ce448bc9f752ddecdf3a

commit a753d2b58c66364e0d0ebcc3543a7af80e5d15f7
Author: Denis Magda 
Date:   2016-11-22T15:48:23Z

IGNITE-4238: Added missing ASF header

commit 93c3ccd01228394f9d95620ccd2c1f68d1e0b22c
Author: devozerov 
Date:   2016-11-23T08:17:58Z

Merge branch 'ignite-1.7.4'

commit b038730ee56a662f73e02bbec83eb1712180fa82
Author: isapego 
Date:   2016-11-23T09:05:54Z

IGNITE-4249: ODBC: Fixed performance issue caused by ineddicient IO 
handling on CPP side. This closes #1254.

commit 86d143bb8bdbdccba9209762b1fd802d5dc40268
Author: Alexander Paschenko 
Date:   2016-11-23T09:58:26Z

IGNITE-2294: Implemented DML.

commit 4ba1386987cdd7ee26c14a6d599d6c6a970ca08a
Author: devozerov 
Date:   2016-11-23T14:56:50Z

Merge branch 'ignite-1.7.4' into ignite-1.8

commit f4524a6a7b86df9cd008dcd22fa5cfa400c3af27
Author: isapego 
Date:   2016-11-23T14:58:41Z

IGNITE-4096: Added ODBC-DML tests. Fixed issues. This closes #1178.

commit 83363d8e0cab93b62f674ce0215082364881254b
Author: isapego 
Date:   2016-11-23T15:07:06Z

IGNITE-4016: ODBC: Example now uses DML. This closes #1265.

commit 4d243251006bc8d1de85d7b6a481976899755a82
Author: isapego 
Date:   2016-11-23T15:11:35Z

IGNITE-3910: ODBC: Implemented SQLDescribeParam. This closes #1269.

commit 91385256a55f083d8973e5d5b0445f28182d36f2
Author: sboikov 
Date:   2016-11-24T07:45:03Z

ignite-3955 added test

commit 7a47a0185d308cd3a58c7bfcb4d1cd548bff5b87
Author: devozerov 
Date:   2016-11-24T08:14:08Z

IGNITE-4270: Allow GridUnsafe.UNALIGNED flag override.

commit bf330251734018467fa3291fccf0414c9da7dd1b
Author: Andrey Novikov 
Date:   2016-11-24T10:08:08Z

Web console beta-6.

commit e43ea5ee9b6982b2b2086fd2a678882d24c1654c
Author: Andrey Novikov 
Date:   2016-11-24T10:12:07Z

Merge branch 'ignite-1.7.4' into 'ignite-1.8'.

commit 7d88c5bfe7d6f130974fab1ed4266fff859afd3d
Author: Andrey Novikov 
Date:   2016-11-24T10:59:33Z

Web console beta-6. Minor fix.

commit d2b915e50c8e3cbe07f565f14d14474342662550
Author: Andrey Novikov 
Date:   2016-11-24T11:01:31Z

Merge branch 'ignite-1.7.4' into 'ignite-1.8'.

commit 4a758d1a6285f9441af7c894e2a31e0df895cb03
Author: isapego 
Date:   2016-11-24T12:49:08Z

IGNITE-4288: ODBC: Fixed DML interoperability. This closes #1272.

commit d5dc5815416cc13f7b2b8a323fa5a39ec95ecb95
Author: isapego 
Date:   2016-11-24T12:53:35Z

IGNITE-4299: ODBC Minor example fix. This closes #1277.

commit 9c6824b4f33fbdead64299d9e0c34365d5d4a570
Author: nikolay_tikhonov 
Date:   2016-11-24T13:27:05Z

IGNITE-3958 Fixed "Client node should not start rest processor".

commit 9326f9a5c081f3ba434dade7e9541c46e4ad1cea
Author: Pavel Tupitsyn 
Date:   2016-11-24T13:32:02Z

IGNITE-4297 .NET: Update NuGet scripts to clean up jars in bin folder

commit c4badeef809851c1ab890e2d6358834f698e94ad
Author: Pavel Tupitsyn 
Date:   2016-11-24T13:32:02Z

IGNITE-4297 .NET: Update NuGet scripts to clean up jars in bin folder

commit 56998e704e9a67760c70481c10c56e72c0a866bb
Author: Konstantin Dudkov 
Date:   2016-10-28T13:27:34Z

ignite-4088 Added methods to create/destroy multiple caches. This closes 
#1174.

(cherry picked from commit f445e7b)

commit fabb77d17859a0a6318c2fe11182ab753e2198e0
Author: Alexander Paschenko 

[GitHub] ignite pull request #1439: IGNITE-4556 .NET: DML example

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-4556 .NET: DML example



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

$ git pull https://github.com/ptupitsyn/ignite ignite-4556

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

https://github.com/apache/ignite/pull/1439.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 #1439


commit e44fa85ddd2e2f3058d6bfa32ea868cd5e6008df
Author: Pavel Tupitsyn 
Date:   2017-01-18T16:03:55Z

IGNITE-4556 .NET: DML example




---
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-4487 - NPE on query execution

[Alexey Goncharuk]

Alexander,

I merged your PR to master, however I had to rewrite the test completely.
Please review my changes carefully for further contributions:
 *  The test was missing Apache License header
 * We do not create Ignite configuration and start nodes manually.
startGrids() takes care of the config. If you need to change ignite
configuration, override the getConfiguration(String) method
 * Do no start threads manually. For async test operations we have many
GridTestUtils#...Multithreaded() methods

2017-01-09 11:07 GMT+03:00 Alexey Goncharuk :

> Alexander,
>
> I left my comments in the ticket.
>
> 2017-01-06 20:35 GMT+03:00 Denis Magda :
>
>> Thanks Alexander.
>>
>> Someone will review and merge your changes in the nearest time. Alex G.,
>> can you do that?
>>
>> —
>> Denis
>>
>> > On Jan 6, 2017, at 5:07 AM, Александр Меньшиков 
>> wrote:
>> >
>> > http://ci.ignite.apache.org/project.html?projectId=IgniteTes
>> ts=projectOverview_IgniteTests=pull%2F1388%2Fmerge
>> >
>> > There are overview of tests. It seems okay. A little unclear because
>> there
>> > are tests which  failed also in master branch.
>> >
>> > 2016-12-29 19:49 GMT+03:00 Denis Magda :
>> >
>> >> 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 <
>> >> https://cwiki.apache.org/confluence/display/IGNITE/How+
>> >> to+Contribute#HowtoContribute-1.CreateGitHubpull-request>
>> >>
>> >> —
>> >> Denis
>> >>
>> >>> On Dec 29, 2016, at 3:45 AM, Александр Меньшиков <
>> sharple...@gmail.com>
>> >> wrote:
>> >>>
>> >>> 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 <
>> alexey.goncha...@gmail.com
>> >>> :
>> >>>
>>  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:15 AM, Александр Меньшиков <
>> >> sharple...@gmail.com
>> >
>> > wrote:
>> >>
>> >>
>> >> Username: sharpler
>> >>
>> >> Full Name: Alexander Menshikov
>> >>
>> >>
>> >>
>> >> 2016-12-27 22:57 GMT+03:00 Denis Magda  > dma...@apache.org>>:
>> >> Alexander,
>> >>
>> >> I need to know your JIRA ID in order to add you to the contributors
>>  list.
>> >>
>> >> As for your questions, this situation might be caused by the race
>> when
>>  a
>> > cache is being stopped and there are still scan queries running in
>> > parallel. So, in general it’s not about data loss.
>> >>
>> >> Sam, Alex G., could you share your thoughts in regards to the
>> proper
>>  fix?
>> >>
>> >> —
>> >> Denis
>> >>
>> >>> On Dec 26, 2016, at 2:43 AM, Александр Меньшиков <
>>  sharple...@gmail.com
>> > > wrote:
>> >>>
>> >>> Hello everyone.
>> >>>
>> >>> I want to pick up *https://issues.apache.org/jir
>> a/browse/IGNITE-4487
>>  <
>> > https://issues.apache.org/jira/browse/IGNITE-4487>
>> >>> > > https://issues.apache.org/jira/browse/IGNITE-4487>>* as my
>> >>> first issue.
>> >>>
>> >>> Please add me as contributor.
>> >>>
>> >>> I already found that: in inner class
>> >>> 'GridCacheQueryAdapter.ScanQueryFallbackClosableIterator' in
>> > constructor is
>> >>> called with method 'init()', but method 'init()' cannot be called
>>  with
>> > an
>> >>> empty field 'nodes'. In source code it looks like:
>> >>>
>> >>> private ScanQueryFallbackClosableIterator(int part,
>> > GridCacheQueryAdapter
>> >>> qry,
>> >>>  GridCacheQueryManager qryMgr, GridCacheContext cctx) {
>> >>>  this.qry = qry;
>> >>>  this.qryMgr = qryMgr;
>> >>>  this.cctx = cctx;
>> >>>  this.part = part;
>> >>>
>> >>>  nodes = fallbacks(cctx.discovery().topologyVersionEx());
>> >>>  // !!! Here nodes.isEmpty()==true, and init() will fail
>> in
>> > the
>> >>> future. !!!
>> >>>  init();
>> >>>  }
>> >>>
>> >>> I can fix it by adding some check in code, but i must know what
>> > behavior
>> >>> are best in this case? As I understand it, the list of nodes is
>> empty
>> > 

[GitHub] ignite pull request #1388: IGNITE-4487: Fixed

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Sort nodes in the ring in order to minimize the number of reconnections

[Александр Меньшиков]

Yakov, as I understand it we need add CLUSTER_REGION_ID for each nodes in
config file. And in fact using some kind of sort in nextNode method (the
search for extreme values to be exact). And the existence of valid
comparator is a sufficient condition to sort nodes to build new correct
ring. So I has thought we will not get any extra benefits (performance or
maintainability) if we close the ability for users to set their sort logic.
Code will a similar in two variants. I has thought if I show this variant
will be easier to see that variant is okay.
But if not, then I can fast change code.

[GitHub] ignite pull request #1438: Ignite 4557

[zstan]

GitHub user zstan opened a pull request:

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

Ignite 4557



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

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

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

https://github.com/apache/ignite/pull/1438.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 #1438


commit 0712a8139c3fd17f6d089ce3ace9bb221e488616
Author: Sergey Sidorov 
Date:   2016-11-25T10:41:02Z

gg-11414: refactoring after core review

commit f5560fe2c3d28c13e58087d8f482ade243dd4c3d
Author: EdShangGG 
Date:   2016-11-27T22:58:09Z

GG-11721 We are losing data if topology is different that when we have 
crushed
-adding WAL-logging of resetting counter in page list meta
-adding WAL-logging of memory recovery
-adding checks of cluster activity state

commit 4809b84e32ddd92354aa2e3187a9b80dc6d314b1
Author: Alexey Goncharuk 
Date:   2016-11-28T09:30:14Z

Merge master into ignite-db-x

commit 32ee31c3d6aaf831d8e18f253fc14f3549947bab
Author: Alexey Goncharuk 
Date:   2016-11-28T09:31:15Z

Merge master into ignite-db-x

commit 1642c00d5c899cbeab2d1ca8e002dc68942a1ac1
Author: Alexey Goncharuk 
Date:   2016-11-28T09:57:19Z

Fixing message IDs after merge

commit 24594d3c02d16090d0f11473b681d0f715df55ed
Author: Alexey Kuznetsov 
Date:   2016-11-28T10:28:26Z

Merge branches 'master' into 'ignite-db-x'.

# Conflicts:
#   
benchmarks/yardstick/src/main/dotnet/gridgain-benchmarks/Properties/AssemblyInfo.cs
#   
modules/core/src/main/java/org/gridgain/grid/internal/processors/license/GridLicenseV2.java
#   
modules/core/src/main/java/org/gridgain/grid/internal/processors/license/GridLicenseV2Adapter.java
#   modules/core/src/main/resources/gridgain.properties
#   
modules/license-gen/src/test/java/org/gridgain/tools/license/GridLicenseGeneratorSelfTest.java
#   modules/platforms/cpp/examples/configure.ac
#   
modules/platforms/dotnet/examples/GridGainExamples/Properties/AssemblyInfo.cs
#   
modules/platforms/dotnet/examples/GridGainExamplesDll/Properties/AssemblyInfo.cs
#   
modules/platforms/dotnet/gridgain-examples-test/Properties/AssemblyInfo.cs
#   modules/platforms/dotnet/gridgain-exe/Properties/AssemblyInfo.cs
#   
modules/platforms/dotnet/gridgain-test-compatibility/Properties/AssemblyInfo.cs
#   modules/platforms/dotnet/gridgain-test-dll/Properties/AssemblyInfo.cs
#   modules/platforms/dotnet/gridgain-test-runner/Properties/AssemblyInfo.cs
#   modules/platforms/dotnet/gridgain-test/Properties/AssemblyInfo.cs
#   modules/platforms/dotnet/gridgain/Properties/AssemblyInfo.cs
#   
modules/visor/src/main/scala/org/gridgain/visor/gui/common/VisorStyledLabel.scala
#   
modules/visor/src/main/scala/org/gridgain/visor/gui/dialogs/connect/VisorConnectDialog.scala
#   
modules/visor/src/main/scala/org/gridgain/visor/gui/dialogs/groupnodes/VisorGroupNodesDialog.scala
#   
modules/visor/src/main/scala/org/gridgain/visor/gui/model/VisorGuiModel.scala
#   
modules/visor/src/main/scala/org/gridgain/visor/gui/model/VisorGuiModelDriver.scala
#   
modules/visor/src/main/scala/org/gridgain/visor/gui/model/data/VisorNode.scala
#   
modules/visor/src/main/scala/org/gridgain/visor/gui/model/impl/VisorGuiModelImpl.scala
#   
modules/visor/src/main/scala/org/gridgain/visor/gui/nodes/VisorSelectCacheNodeDialog.scala
#   
modules/visor/src/main/scala/org/gridgain/visor/gui/nodes/panels/VisorNodesTableModel.scala
#   
modules/visor/src/main/scala/org/gridgain/visor/gui/tabs/data/VisorCachesActions.scala
#   
modules/visor/src/main/scala/org/gridgain/visor/gui/tabs/data/VisorCachesPanel.scala
#   
modules/visor/src/main/scala/org/gridgain/visor/gui/tabs/dr/VisorDrSenderDataNodesTableModel.scala
#   
modules/visor/src/main/scala/org/gridgain/visor/gui/tabs/dr/VisorDrToggleReplicationDialog.scala
#   
modules/visor/src/main/scala/org/gridgain/visor/gui/tabs/sql/VisorSqlViewerTab.scala
#   
modules/visor/src/test/scala/org/gridgain/visor/gui/driver/VisorCommonDriverSpec.scala
#   modules/yardstick/dotnet/Properties/AssemblyInfo.cs

commit 523640770967ac000171171314457b81138e45c2
Author: Alexey Goncharuk 
Date:   2016-11-28T11:01:05Z

Fixing after merge

commit ae93caade2750719966d6b2a3ce0b52f3f09e96d
Author: Alexey Goncharuk 
Date:   2016-11-28T11:21:51Z

Fixing after merge

commit 3d28b68f61d3823b0831c819feeea2f88c6e5349
Author: Dmitriy Govorukhin 
Date:   2016-11-28T12:02:27Z

ignite-gg-11650  active - > 

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

[Yakov Zhdanov]

Alexander, I was against any comparator and user defined logic exactly for
reason that comparison may be inconsistent. After long discussion and
consensus you implement approach with comparator. Can you please explain
why you did not just add logic to compare the value of CLUSTER_REGION_ID
node attribute?

--Yakov

2017-01-18 16:48 GMT+03:00 Александр Меньшиков :

> I done that things:
>
> -- Add to TcpDiscoverySpi field Comparator
> nodeComparator for load custom comparators from config file like bean.
> -- Add implementation with old behavior: BaseNodeComparator
> -- Add region id implementation: RegionNodeComparator which get map from
> IP address to region ID in constructor.
> -- Modified TcpDiscoveryNodesRing#nextNode for using nodeComparator for
> find next node.
>
> You can see that in PR: https://github.com/apache/ignite/pull/1436
>
> Main question is: how to test it?
>
> For my local test i just changed BaseNodeComparator with this odd
> comparator:
>
> new Comparator() {
> @Override
> public int compare(TcpDiscoveryNode t1, TcpDiscoveryNode
> t2) {
> //shuffle nodes
> final int ans = 
> Long.compare((t1.internalOrder()*3L+13L)%4L,
> (t2.internalOrder()*3L+13L)%4L);
> return (ans==0)?t1.compareTo(t2):ans;
> }
> };
>
> It's looking scary, but in fact it just consistently shuffle nodes. If you
> have 4 nodes with topology versions 1, 2, 3 and 4, it will be ring: 1-4-3-2.
>
> So I think if we just using in old test this shuffle comparator and
> nothing gone wrong it's good enough.
>
> But any way I don't know how to add that to tests.
>
> And may be we need some test for custom comparators. But in fact comparators
> just must be valid Java comparator and work the same on all nodes.
>
> Any comments are welcome.
>

[GitHub] ignite pull request #1437: IGNITE-4550: Move service deployment to certain t...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-4550: Move service deployment to certain test

Fixed

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

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

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

https://github.com/apache/ignite/pull/1437.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 #1437


commit 7724b62bf44e7bd8cbb8ce1fb3aa20b96f1fa410
Author: Andrey V. Mashenkov 
Date:   2017-01-18T13:48:07Z

Fixed.

commit 8c48cff7202d4f83b40ac3708db4baeafaf0cae6
Author: Andrey V. Mashenkov 
Date:   2017-01-18T13:48:33Z

Fixed.




---
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: Sort nodes in the ring in order to minimize the number of reconnections

[Александр Меньшиков]

I done that things:

-- Add to TcpDiscoverySpi field Comparator nodeComparator
for load custom comparators from config file like bean.
-- Add implementation with old behavior: BaseNodeComparator
-- Add region id implementation: RegionNodeComparator which get map from IP
address to region ID in constructor.
-- Modified TcpDiscoveryNodesRing#nextNode for using nodeComparator for
find next node.

You can see that in PR: https://github.com/apache/ignite/pull/1436

Main question is: how to test it?

For my local test i just changed BaseNodeComparator with this odd
comparator:

new Comparator() {
@Override
public int compare(TcpDiscoveryNode t1, TcpDiscoveryNode
t2) {
//shuffle nodes
final int ans =
Long.compare((t1.internalOrder()*3L+13L)%4L,
(t2.internalOrder()*3L+13L)%4L);
return (ans==0)?t1.compareTo(t2):ans;
}
};

It's looking scary, but in fact it just consistently shuffle nodes. If you
have 4 nodes with topology versions 1, 2, 3 and 4, it will be ring: 1-4-3-2.

So I think if we just using in old test this shuffle comparator and nothing
gone wrong it's good enough.

But any way I don't know how to add that to tests.

And may be we need some test for custom comparators. But in fact comparators
just must be valid Java comparator and work the same on all nodes.

Any comments are welcome.

[GitHub] ignite pull request #1436: Add extension point to reordering nodes by custom...

[SharplEr]

GitHub user SharplEr opened a pull request:

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

Add extension point to reordering nodes by custom comparator.

-- Add to TcpDiscoverySpi field Comparator nodeComparator 
for load custom comparators from config file like bean.
-- Add implementation with old behavior: BaseNodeComparator
-- Add region id implementation: RegionNodeComparator which get map from IP 
address to region ID in constructor.
-- Modified TcpDiscoveryNodesRing#nextNode for using nodeComparator for 
find next node.

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

$ git pull https://github.com/SharplEr/ignite ignite-4501

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

https://github.com/apache/ignite/pull/1436.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 #1436


commit 2290d3fa3304781f2d7980ecb076902beb859a88
Author: Alexander Menshikov 
Date:   2017-01-18T12:34:26Z

Add extension point to reordering nodes by custom comparator.




---
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-4559) .NET: Use BinaryArrayIdentityResolver by default

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4559:
--

 Summary: .NET: Use BinaryArrayIdentityResolver by default
 Key: IGNITE-4559
 URL: https://issues.apache.org/jira/browse/IGNITE-4559
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
 Fix For: 2.0


Same as IGNITE-4558 for .NET



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

[jira] [Created] (IGNITE-4560) .NET: Use BinaryArrayIdentityResolver by default

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4560:
--

 Summary: .NET: Use BinaryArrayIdentityResolver by default
 Key: IGNITE-4560
 URL: https://issues.apache.org/jira/browse/IGNITE-4560
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
 Fix For: 2.0


Same as IGNITE-4558 for .NET



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

[jira] [Created] (IGNITE-4558) Use BinaryArrayIdentityResolver by default

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4558:
--

 Summary: Use BinaryArrayIdentityResolver by default
 Key: IGNITE-4558
 URL: https://issues.apache.org/jira/browse/IGNITE-4558
 Project: Ignite
  Issue Type: Improvement
  Components: binary
Reporter: Pavel Tupitsyn
 Fix For: 2.0


Currently if there is no configured 
{{BinaryTypeConfiguration.IdentityResolver}}, we call Object.hashCode().

This is not consistent with DML, and there is a warning:
{code}
Binary object's type does not have identity resolver explicitly set, therefore 
BinaryArrayIdentityResolver is used to generate hash codes for its instances, 
and therefore hash code of this binary object will most likely not match that 
of its non serialized form. For finer control over identity of this type, 
please update your BinaryConfiguration accordingly.
{code}

In 2.0 we should use {{BinaryArrayIdentityResolver}} by default.



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

[jira] [Created] (IGNITE-4557) Wrong method is called on rebalancing.

[Alexei Scherbakov (JIRA)]

Alexei Scherbakov created IGNITE-4557:
-

 Summary: Wrong method is called on rebalancing.
 Key: IGNITE-4557
 URL: https://issues.apache.org/jira/browse/IGNITE-4557
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.6
Reporter: Alexei Scherbakov
Assignee: Alexei Scherbakov
Priority: Critical
 Fix For: 2.0


During rebalancing the following code might be called from 
{{GridDhtPartitionDemander:695}}:

{noformat}
for (Integer miss : supply.missed()) {
  if (cctx.affinity().localNode(miss, topVer))
fut.partitionMissed(id, miss);
}
{noformat}

The problem is in wrong polymorphic call to

{noformat}
public boolean localNode(Object key, AffinityTopologyVersion topVer)}}
{noformat}

Instead the following must be called:

{noformat}
public boolean localNode(int part, AffinityTopologyVersion topVer);.
{noformat}

Also a codebase must be verified for existing similar problems and its better 
to rename both methods to keyLocalNode and partitionLocalNode to avoid 
confusion.






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

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

[Sally Khudairi]

Hello everyone --as promised, we are live:
 - ASF "Foundation" blog https://s.apache.org/Slah
 - @TheASF Twitter feed https://twitter.com/TheASF/status/821660992522297344
 - NEW! ASF LinkedIn page 
https://www.linkedin.com/company/the-apache-software-foundation
... as well as to announce@ and our dedicated media/analyst list. This will 
appear on the apache.org homepage and archives during the next auto-update, 
which should take place within the hour.
Thanks again for all your help and a job well done!
Warmly,
Sally = = = = =  vox +1 617 921 8656gvox +1 646 598 4616skype sallykhudairi

  From: Sally Khudairi 
 To: Denis Magda ; Sally Khudairi  
Cc: "dev@ignite.apache.org" 
 Sent: Tuesday, January 17, 2017 1:52 PM
 Subject: Re: [ANNOUNCE] Apache Ignite 1.8.0 Released
   
OK great; thanks, Denis!
I've accepted almost all suggestions, except for the ones that align with ASF 
editorial house style (= "look" vs. meaning).
Kind thanks,Sally


[From the mobile; please excuse top-posting, spelling/spacing errors, and 
brevity]


 
 
 On Tue, Jan 17, 2017 at 13:41, Denis Magda wrote:  Hi Sally,
I’ve finished on my side. Please see my suggestions in the google doc.
If anyone else is willing to review the announcement please do it by 18.00 PM 
EST (15.00 PST).
—Denis

On Jan 17, 2017, at 9:20 AM, Sally Khudairi  wrote:
Hi everyone --just confirming that we'll need to lock in the copy in ~6 hours 
in order to announce tomorrow morning.
Denis, if you can please forward the copy when ready so the PMC has a chance to 
review in time, that would be great.
Thanks so much,
Sally = = = = =  vox +1 617 921 8656gvox +1 646 598 4616skype sallykhudairi

  From: Sally Khudairi 
 To: Denis Magda ; "s...@apache.org"  
Cc: "dev@ignite.apache.org" 
 Sent: Sunday, January 15, 2017 9:20 AM
 Subject: Re: [ANNOUNCE] Apache Ignite 1.8.0 Released
  
Excellent. Thank you, Denis.
Enjoy the day!
-Sally


[From the mobile; please excuse top-posting, spelling/spacing errors, and 
brevity]


 
 
 On Sun, Jan 15, 2017 at 9:12, Denis Magda wrote:  Thanks, 
Sally. Confirm that I could access and edit the doc. 
Sure, I’ll finish the editing by that time. Most likely this will be the first 
thing to do on Tuesday.
—Denis

On Jan 15, 2017, at 3:07 AM, Sally Khudairi  wrote:
Oh wow --Denis, thank you!
I must say, the documentation on Ignite is exhaustive and comprehensive, so 
pulling things together was an "embarrassment of riches" experience . Gold 
Star to the PMC --I'll definitely use this as an example for other projects to 
emulate.

OK...I just sent you editing credentials, and look forward to locking in the 
copy hopefully by 6PM ET on Tuesday so we can go live Wednesday morning.
Does that work for you?
Kind thanks again,Sally

[From the mobile; please excuse top-posting, spelling/spacing errors, and 
brevity]


 
 
 On Sat, Jan 14, 2017 at 23:38, Denis Magda wrote:  Sally, 
You understood everything perfectly well producing such a clear and great 
article! Not sure that anyone could write better ;)
Please give editing permissions to my google account (magda7...@gmail.com). 
I’ll fill in the missing part.
—Denis

On Jan 14, 2017, at 9:01 AM, Sally Khudairi  wrote:
Hello, everyone --as promised, below is the draft so far. Here's hoping I 
understood everything correctly 
Kindly note that we'll need to fill in the "@@" under the hood section on v1.8 
(this part can be technical and developer-focused, whilst the rest of the 
document should be tech-lite = understandable for journalists who are geeky but 
not technologists). I'll be happy to provide editing credentials on the 
googledoc to those requesting it.
Do keep in mind that this is not a press release, so the format is different 
from what we're used to (I launched the "Have you met...?" series with 
Mahout[1] back in 2010 to great media interest: coverage within 24 hours). We 
can also work together on establishing a template for you to use for future 
project announcements.
As always, comments/corrections/additions welcome!
Thanks so much,Sally
[1] 
= = =
The ASF asks: Have you met Apache Ignite?
Since 1999, The Apache Software Foundation (ASF) has been recognized as a 
leading source for an array of Open Source software and tools that meet the 
demand for interoperable, adaptable, and sustainable solutions. The 
all-volunteer ASF develops, stewards, and incubates dozens of enterprise-grade 
Open Source projects that power mission-critical applications in financial 
services, aerospace, publishing, government, healthcare, research, 
infrastructure, and more. From Abdera to ZooKeeper, the demand for ASF's 
reliable, community-driven software continues to grow dramatically across many 
categories, including Cloud, IoT, 

[jira] [Created] (IGNITE-4556) .NET: DML documentation and example

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4556:
--

 Summary: .NET: DML documentation and example
 Key: IGNITE-4556
 URL: https://issues.apache.org/jira/browse/IGNITE-4556
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.9


See [~dmagda] comment in IGNITE-4045:

{code}
 In general, it makes sense to introduce SQL Grid paragraph in .NET as we did 
for Java and document only those pieces that are related to .NET. For the rest 
you can refer to Java doc from .NET doc.
In addition, it will be great if you add a DML example similar to the one we 
have in Java.
{code}



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

Re: scripting languages base cases using swig

[Sergi Vladykin]

I think its worth trying. Recently on userlist someone requested Golang
integration. If we can achieve this with SWIG relatively easy, then why not.

Sergi

2017-01-18 10:55 GMT+03:00 Evgeniy Stanilovskiy 
:

> Hi Denis,
>
> I don`t see any problem here, i have to speak with @vozerov about this
> issue and he recommends me to write it into dev list. All problems that i
> have with swig is :
> 1. jni overhead (no miracle here ...)
> 2. light troubles with collections API wrapping, like std::map, std::list
> and so on.
>
> Partially my open source FreeLing java wrapper you can see here
> https://github.com/TALP-UPC/FreeLing/tree/master/APIs/java
>
> std_list.i - little stub :) i have talking about.
>
>
> Hi Evgeniy,
>>
>> Presently we’re trying to fill this gap offering SQL Grid [1]. In a
>> nutshell, you can connect to an Ignite cluster from your favorite language
>> or tool with ODBC/JDBC drivers and work with the cluster using SQL SELECT,
>> INSERT, UPDATE, DELETE statements.
>>
>> Here is how everything works for PHP that is not natively supported by
>> Ignite:
>> https://dzone.com/articles/apache-ignite-enables-full-fledge
>> d-sql-support-for
>>
>> However, as for SWIG. Do you think it’s feasible to implement on top of
>> Ignite.C++ client which is tightly coupled with JVM?
>>
>> [1] https://apacheignite.readme.io/docs/sql-grid <
>> https://apacheignite.readme.io/docs/sql-grid>
>>
>> —
>> Denis
>>
>> On Jan 16, 2017, at 11:46 PM, Evgeniy Stanilovskiy <
>>> estanilovs...@gridgain.com> wrote:
>>>
>>> Hi all.
>>> Not so long ago i had to know that ignite had reduced functionality
>>> support in scripting languages.
>>> So, idea was to take an existing C++ client and using SWIG (
>>> http://www.swig.org) as automatic wrapper, generate clients for absence
>>> scripting languages.
>>> What do you think about this case ?
>>>
>>> Thanks !
>>>
>>