Hello

2017-04-08 Thread Ritesh Modi
Hello Ignite community,

My name is Ritesh and I want to contribute to project. I can start with Ticket
4867: CacheMetricsSnapshot ignores 'size' and 'keySize' fields
 reported by Dmitry
Karachentsev.

I've forked github apache/ignite and cloned in my local. I want to know in
which module can I find CacheMetricsSnapshot &
CacheClusterMetricsMXBeanImpl.

If this ticket is taken by someone else then let me know from which ticket
can I start.

Regards,
Ritesh


Re: IGNITE-2558 PR is ready to review (NearCacheConfiguration should not extend MutableConfiguration)

2017-04-08 Thread Valentin Kulichenko
Hi Maxim,

I merged your changes to master. Thanks for the contribution!

-Val

On Thu, Apr 6, 2017 at 1:33 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Maxim,
>
> I will take a look today or tomorrow.
>
> -Val
>
> On Tue, Apr 4, 2017 at 7:40 AM, Kozlov Maxim  wrote:
>
>> Create ticket https://issues.apache.org/jira/browse/IGNITE-4910 <
>> https://issues.apache.org/jira/browse/IGNITE-4910> and fix PR.
>>
>> > 4 апр. 2017 г., в 17:06, Kozlov Maxim 
>> написал(а):
>> >
>> > Valentin, of course. I'll let you know how I'll do it.
>> >
>> >> 4 апр. 2017 г., в 16:38, Valentin Kulichenko <
>> valentin.kuliche...@gmail.com >
>> написал(а):
>> >>
>> >> Maxim,
>> >>
>> >> It looks like you added copyOnRead property on configuration, but I'm
>> >> pretty sure that currently it will be ignored. Basically, it's a new
>> >> feature and I'm OK if we do this as a separate task sometime later
>> (e.g. in
>> >> 2.1). Can you create a ticket and remove the property for now?
>> >>
>> >> -Val
>> >>
>> >> On Tue, Apr 4, 2017 at 3:04 AM, Kozlov Maxim > > wrote:
>> >>
>> >>> Hi igniters,
>> >>>
>> >>> Please review if someone has time.
>> >>> https://issues.apache.org/jira/browse/IGNITE-2558 <
>> https://issues.apache.org/jira/browse/IGNITE-2558> <
>> >>> https://issues.apache.org/jira/browse/IGNITE-2558 <
>> https://issues.apache.org/jira/browse/IGNITE-2558>>
>> >>> https://github.com/apache/ignite/pull/1701 <
>> https://github.com/apache/ignite/pull/1701> > https://github.com/apache/>
>> >>> ignite/pull/1701>
>> >>>
>> >>> --
>> >>> Best Regards,
>> >>> Max K.
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >
>> > --
>> > Best Regards,
>> > Max K.
>> >
>> >
>> >
>> >
>>
>> --
>> Best Regards,
>> Max K.
>>
>>
>>
>>
>>
>


Re: Apache Ignite 2.0 Release

2017-04-08 Thread Valentin Kulichenko
Guys,

There is no branch for 2.0 right now, correct? If I want to add something
there, do I just merge to master?

-Val

On Sat, Apr 8, 2017 at 10:18 AM, Alexander Paschenko <
alexander.a.pasche...@gmail.com> wrote:

> I've fixed https://issues.apache.org/jira/browse/IGNITE-4354, PR is
> https://github.com/apache/ignite/pull/1759.
> Pavel, thank you very much for bringing that to my attention.
>
> - Alex
>
> 2017-04-07 20:28 GMT+03:00 Sergi Vladykin :
> > A bunch of SQL related tickets is delayed until H2 release on the next
> week.
> >
> > Sergi
> >
> > 2017-04-07 19:36 GMT+03:00 Alexey Goncharuk  >:
> >
> >> Folks,
> >>
> >> The status of ignite-3477 is as follows: we've fixed almost all tests
> and
> >> currently waiting for ignite-4535 and ignite-4534 to be merged, which
> will
> >> happen once TC for those branches is completed. This should happen over
> the
> >> weekend.
> >>
> >> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov :
> >>
> >> >  I've prepared
> >> >
> >> >  IGNITE-4349  -
> >> > Discontinue the schema-import utility
> >> >
> >> > Anton, could you review my changes related to Ignite *build*?
> >> > See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163
> >> >
> >> >
> >> > --
> >> > Alexey Kuznetsov
> >> >
> >>
>


[GitHub] ignite pull request #1701: IGNITE-2558: Remove extends MutableConfiguration,...

2017-04-08 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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: Apache Ignite 2.0 Release

2017-04-08 Thread Alexander Paschenko
I've fixed https://issues.apache.org/jira/browse/IGNITE-4354, PR is
https://github.com/apache/ignite/pull/1759.
Pavel, thank you very much for bringing that to my attention.

- Alex

2017-04-07 20:28 GMT+03:00 Sergi Vladykin :
> A bunch of SQL related tickets is delayed until H2 release on the next week.
>
> Sergi
>
> 2017-04-07 19:36 GMT+03:00 Alexey Goncharuk :
>
>> Folks,
>>
>> The status of ignite-3477 is as follows: we've fixed almost all tests and
>> currently waiting for ignite-4535 and ignite-4534 to be merged, which will
>> happen once TC for those branches is completed. This should happen over the
>> weekend.
>>
>> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov :
>>
>> >  I've prepared
>> >
>> >  IGNITE-4349  -
>> > Discontinue the schema-import utility
>> >
>> > Anton, could you review my changes related to Ignite *build*?
>> > See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163
>> >
>> >
>> > --
>> > Alexey Kuznetsov
>> >
>>


[GitHub] ignite pull request #1759: IGNITE-4354

2017-04-08 Thread alexpaschenko
GitHub user alexpaschenko opened a pull request:

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

IGNITE-4354

Consistent logic to initialize BinaryObjectBuilderImpl.assignedVals field

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

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

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

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


commit 48ab0eb3c40f37c3cba421dc43f695884aadf797
Author: Alexander Paschenko 
Date:   2017-04-08T17:09:39Z

IGNITE-4354 Consistent logic to initialize 
BinaryObjectBuilderImpl.assignedVals field




---
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 #1758: IGNITE-4534: Implement offheap eviction policies ...

2017-04-08 Thread glukos
GitHub user glukos opened a pull request:

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

IGNITE-4534: Implement offheap eviction policies based on page memory

Postreview.

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

$ git pull https://github.com/gridgain/apache-ignite 
ignite-4534-from-3477-master

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

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


commit 98d92d89d69497172a6d33d88c17c1b05396ae04
Author: Ivan Rakov 
Date:   2017-04-04T18:53:35Z

IGNITE-4534: Implement offheap eviction policies based on page memory

commit 2235c7df11042b7c5920889c59ded17bab7bafff
Author: sboikov 
Date:   2017-04-05T11:14:36Z

ignite-4534 review

commit a2cead5342971771f63e91d4564ea738c73bd5fe
Author: Ivan Rakov 
Date:   2017-04-06T10:24:42Z

IGNITE-4534: Postreview.

commit 9cdf332a4931a94602d7ef723def6e338d7a73d0
Author: Ivan Rakov 
Date:   2017-04-06T14:00:09Z

IGNITE-4534: Postreview

commit c824b35293a9e131aec4848323bca94acbc7c2da
Author: Dmitriy Govorukhin 
Date:   2017-04-07T12:44:54Z

ignite-3477-master mute test

commit 3cd21e38b39ebe3966b601a1ab7d0f8a5af30cb6
Author: Ivan Rakov 
Date:   2017-04-07T13:44:08Z

IGNITE-4534: Postreview

commit 0a65588275e27d8a159f114adb44cf00c8df85ae
Author: Ivan Rakov 
Date:   2017-04-07T13:55:34Z

Merge branch 'ignite-3477-master' into ignite-4534-from-3477-master

# Conflicts:
#   modules/core/src/main/java/org/apache/ignite/internal/pagemem/Page.java
#   
modules/core/src/main/java/org/apache/ignite/internal/pagemem/impl/PageNoStoreImpl.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/CacheOffheapEvictionManager.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/database/CacheDataRowAdapter.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/database/freelist/FreeListImpl.java

commit aa66de672fde2ea5b615400132a71248c240bca9
Author: Konstantin Dudkov 
Date:   2017-04-07T14:18:53Z

remove GridCache(Atomic|Dht|Near)ExpiredEntriesPreloadSelfTest

commit f684af89fa83c07f2264523915d6f0e42fe1fad2
Author: Ivan Rakov 
Date:   2017-04-07T16:19:21Z

IGNITE-4534: Fixing issues after merge with Page deletion

commit e09e0f52d72325c0a4b6e4c95b577284cf5dc15d
Author: Ivan Rakov 
Date:   2017-04-08T12:34:03Z

Merge branch 'ignite-3477-master' into ignite-4534-from-3477-master

commit 83b4fff81797dcca27ea2a7dba80cc475f3d7838
Author: Ivan Rakov 
Date:   2017-04-08T12:36:17Z

IGNITE-4534: Method for acquiring force read lock is moved to interface

commit 48a891de3b907f018ec0c6c3c3a9e7f03c4e88c0
Author: Ivan Rakov 
Date:   2017-04-08T13:57:38Z

Merge branch 'ignite-3477-master-apache' into ignite-4534-from-3477-master

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/database/IgniteCacheDatabaseSharedManager.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/database/MemoryPolicy.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/database/freelist/FreeListImpl.java
#   
modules/core/src/test/java/org/apache/ignite/internal/processors/database/FreeListImplSelfTest.java

commit 9693545615679687f99651c552ffb8d391d6d203
Author: Ivan Rakov 
Date:   2017-04-08T14:21:19Z

IGNITE-4534: Fixing minors after merge.




---
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: Hello All

2017-04-08 Thread Valentin Kulichenko
Hi Rishikesh,

I added you as a contributor, you can assign ticket to yourself now. Please
refer to [1] and [2] for detailed information about our process.

Welcome to the community!

[1] https://ignite.apache.org/community/contribute.html#contribute
[2] https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

-Val

On Fri, Apr 7, 2017 at 2:50 PM, rishi007bansod 
wrote:

> Hi all!
>
> My name is Rishikesh, I am new to this community. I want to contribute
> issue
> - IGNITE-4043( https://issues.apache.org/jira/browse/IGNITE-4043
>   ) . I have subscribed
> to Ignite JIRA, my username is rishi007bansod. Please guide me regarding
> how
> to contribute and which codes should I look at first?
>
> Thanks,
> Rishikesh
>
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/Hello-All-tp16289.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>


[GitHub] ignite pull request #1731: IGNITE-4534, up-to-date with ignite-3477-master

2017-04-08 Thread glukos
Github user glukos closed the pull request at:

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


---
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 #1674: IGNITE-4534: Implement offheap eviction policies ...

2017-04-08 Thread glukos
Github user glukos closed the pull request at:

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


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