[ANNOUNCE] Apache Ignite 1.7.0 Released

[Denis Magda]

The Apache Ignite Community is pleased to announce the release of Apache Ignite 
1.7.0.

Apache Ignite In-Memory Data Fabric [1] is a high-performance, integrated and 
distributed in-memory platform for computing and transacting on large-scale 
data sets in real-time, orders of magnitude faster than possible with 
traditional disk-based or flash-based technologies.

The Fabric is a collection of independent and well integrated components some 
of which are the following:  
Advance Clustering
Data Grid
Compute Grid
Streaming & CEP
Service Grid

Apache Ignite 1.7.0 incorporates many improvements and bug fixes that are 
listed in the release notes [2].

Among the changes we have the one that we’re proud of and happy to tell the 
world about - the non-collocated distributed SQL joins [3]. This feature opens 
new horizons for Apache Ignite allowing its users executing the whole range of 
imaginable SQL queries covering all the possible and tricky use cases. You can 
read more details about this in the following blog post:
http://dmagda.blogspot.com/2016/08/big-change-in-apache-ignite-17-welcome.html 

 

If you’re ready to make your hands dirty with Apache Ignite 1.7.0 then the 
downloads of source and binary distributions as well as Maven artifacts' 
versions are listed in the following download section:
https://ignite.apache.org/download.cgi 

Please let us know [4] if you encounter any problems.

Regards,

The Apache Ignite Community

[1] https://ignite.apache.org 
[2] https://github.com/apache/ignite/blob/master/RELEASE_NOTES.txt 

[3] 
https://apacheignite.readme.io/docs/sql-queries#non-collocated-distributed-joins
 

[4] https://ignite.apache.org/community/resources.html#ask 

Re: Greeting from Jason

[Denis Magda]

Hi Jason,

Welcome to the Ignite community!

You should get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Once you got familiar and were able to run a few examples, you should pick
a Jira ticket you would like to start on. Send an email to the dev list, so
we can add you as a contributor in Jira.

You can find interesting tickets to get started here:
https://ignite.apache.org/community/contribute.html#pick-ticket

Looking forward to your contributions!

Regards,
Denis

> On Aug 25, 2016, at 8:56 PM, laoshe  wrote:
> 
> Hi everyone, glad to join you. 
> My name is Jason TAN, i'm now working in a tech company in china.
> I am very interest in ignite - the new in memory data fabric - and i have 
> studied it for a few days. I hope i can make some attributions to ignite, 
> thanks.
> 
> 
> Regards,
> Jason

Re: Hello from Austin

[Denis Magda]

Hello Austin,

Welcome to the Ignite community!

You should get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Once you got familiar and were able to run a few examples, you should pick
a Jira ticket you would like to start on. Send an email to the dev list, so
we can add you as a contributor in Jira.

You can find interesting tickets to get started here:
https://ignite.apache.org/community/contribute.html#pick-ticket

Looking forward to your contributions!

Regards,
Denis

> On Aug 26, 2016, at 7:54 AM, Austin Kuo  wrote:
> 
> Hi all,
> This is Austin. I am a student in Taiwan. I participated GSoC 2016 and
> found it interesting to contribute to open source therefore I wanna  work
> on ignite.  :)
> 
> Regards,
> Austin

[GitHub] ignite pull request #995: IGNITE-3788: Fix flapping test

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-3788: Fix flapping test



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

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

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

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


commit b5f594124dbdc75525bdd2c92fc49b9e126e60ab
Author: ashutak 
Date:   2016-05-18T17:47:26Z

ignite-3056: Service implementation class is required even if it's not 
expected to be deployed on current node (fixed)

commit c9416ed9b58bbb2287e896cc5860177939c4b3ed
Author: nikolay_tikhonov 
Date:   2016-05-20T09:54:55Z

Fixed IGNITE-3004 "Implement config variations test for ContinuousQueries"

commit 1ebbd57b74eef1abeb99fa9427667da17db9d01a
Author: sboikov 
Date:   2016-05-23T06:52:43Z

ignite-2528 Removed cache blocking operations from kernal write lock.

This closes #730
(cherry picked from commit f83a5f7)

commit 40a27e714d0bf62a26a35c90c68a020dbf0256c7
Author: sboikov 
Date:   2016-05-23T04:28:55Z

IGNITE-3175 BigDecimal fields are not supported if query is executed from 
IgniteRDD
(cherry picked from commit f2b390a)

commit 8e49e7013ea378c3040e1aa2d9494196d0833e40
Author: sboikov 
Date:   2016-05-23T16:42:45Z

ignite-2899 Fixed issues with 'keepBinary' handling. This closes #593.
(cherry picked from commit ee7e2c7)

commit 07611bd19beaf73a54f0627a6d8a71c3a1a09874
Author: sboikov 
Date:   2016-05-23T21:07:05Z

ignite-2620 Fixed entry expiration handling
(cherry picked from commit 46892c7)

commit 54e432e9bb6927351ea45d85b94965925a8351c7
Author: sboikov 
Date:   2016-05-23T18:08:14Z

ignite-2899 Fixed issues with 'keepBinary' handling, added test.
(cherry picked from commit e47440d)

commit c8269da30a1d55f06531857c52d254268056e84e
Author: sboikov 
Date:   2016-05-24T08:14:03Z

ignite-2620: Need override 'unswap' for detached entry.
(cherry picked from commit f7b376b)

commit e1ec0dedab0221b53dd11f2854c8c88b2641d147
Author: sboikov 
Date:   2016-05-24T11:31:43Z

IGNITE-2865 Continuous query event passed to filter should be immutable for 
users. This closes #744.
(cherry picked from commit 046657b)

commit 727afc87dce6c26756b56620c2aaccc3a3d0117e
Author: Vladislav Pyatkov 
Date:   2016-05-25T05:29:00Z

IGNITE-2667: Allow to start caches in PRIVATE and ISOLATED deployment modes 
when BinaryMarshaller is used

commit 183620cd31095dcd92471927cccf8741e3b63ed7
Author: nikolay_tikhonov 
Date:   2016-05-25T06:47:14Z

IGNITE-3168 Added idle timeout property.

commit 30aa287b881d4f9dc3fd5eec9840eab8d9a20828
Author: sboikov 
Date:   2016-05-24T13:57:20Z

ignite-2620 Skip empty entries in GridCacheMapEntry.onTtlExpired
(cherry picked from commit 6fc274a)

commit e2db87bb1b6c71d7978af17e9f2005ba1c661ab4
Author: sboikov 
Date:   2016-05-25T07:06:43Z

Added trace logging for entry/offheap updates.
(cherry picked from commit 9b2767f)

commit 6fcc7a41d8676956983792717483318b85781479
Author: MaBiao 
Date:   2016-05-25T09:54:40Z

IGNITE-2538 - IgniteRDD count() and isEmpty() method use IgniteCache API

commit e274d44a37fd1269e7a3a5fe1ee6139fd0b0
Author: Denis Magda 
Date:   2016-05-26T11:57:52Z

IGNITE-3188: Binary marshaller doesn't unmarshal a void type (added tests)

commit 6687e2bfb9627ce08c1c258527e2927606a500ed
Author: Yakov Zhdanov 
Date:   2016-05-13T08:48:00Z

review IGNITE-2708 Need to validate that SPIs are started only once
(cherry picked from commit cd063da)

commit 40a41fc50bdb73d50e2aa13da8203784be98e38a
Author: Yakov Zhdanov 
Date:   2016-05-13T08:59:02Z

reverting review IGNITE-2708 Need to validate that SPIs are started only 
once
(cherry picked from commit bf561e1)

commit d05786d8bfc8177223b6db9a98bd3c8170b6bcf1
Author: Ryan Zhao 
Date:   2016-05-13T09:00:43Z

review IGNITE-2708 Need to validate that SPIs are started only once (commit 
with proper author)
(cherry picked from commit 98338ff)

commit 9d937ca34775f39b46568eb3fca4585ce00a0fb1
Author: Yakov Zhdanov 
Date:   2016-05-13T09:54:01Z

review IGNITE-2708 Need to validate that SPIs are started only once (added 
logic to protect properly started grids)
(cherry picked from commit b8d624a)

commit edc2947d7340cac4a3c90fa726c23d5d47798ab9
Author: 

[jira] [Created] (IGNITE-3788) Test flapping: CodeGeneratorTest.testConfigGeneration

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-3788:


 Summary: Test flapping: CodeGeneratorTest.testConfigGeneration
 Key: IGNITE-3788
 URL: https://issues.apache.org/jira/browse/IGNITE-3788
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.6
Reporter: Andrew Mashenkov
Assignee: Andrew Mashenkov
Priority: Minor


It seems like CodeGeneratorTest.testConfigGeneration check results of method 
testPojoGeneration invokation. So, testConfigGeneration flapping due to there 
is no method invokation order guarantee.






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

Hello from Austin

[Austin Kuo]

Hi all,
This is Austin. I am a student in Taiwan. I participated GSoC 2016 and
found it interesting to contribute to open source therefore I wanna  work
on ignite.  :)

Regards,
Austin

[GitHub] ignite pull request #994: Ignite-2974: ODBC: Implement fine-grained NIO serv...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

Ignite-2974: ODBC: Implement fine-grained NIO server configuration.

... implemented

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

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

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

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


commit b5f594124dbdc75525bdd2c92fc49b9e126e60ab
Author: ashutak 
Date:   2016-05-18T17:47:26Z

ignite-3056: Service implementation class is required even if it's not 
expected to be deployed on current node (fixed)

commit c9416ed9b58bbb2287e896cc5860177939c4b3ed
Author: nikolay_tikhonov 
Date:   2016-05-20T09:54:55Z

Fixed IGNITE-3004 "Implement config variations test for ContinuousQueries"

commit 1ebbd57b74eef1abeb99fa9427667da17db9d01a
Author: sboikov 
Date:   2016-05-23T06:52:43Z

ignite-2528 Removed cache blocking operations from kernal write lock.

This closes #730
(cherry picked from commit f83a5f7)

commit 40a27e714d0bf62a26a35c90c68a020dbf0256c7
Author: sboikov 
Date:   2016-05-23T04:28:55Z

IGNITE-3175 BigDecimal fields are not supported if query is executed from 
IgniteRDD
(cherry picked from commit f2b390a)

commit 8e49e7013ea378c3040e1aa2d9494196d0833e40
Author: sboikov 
Date:   2016-05-23T16:42:45Z

ignite-2899 Fixed issues with 'keepBinary' handling. This closes #593.
(cherry picked from commit ee7e2c7)

commit 07611bd19beaf73a54f0627a6d8a71c3a1a09874
Author: sboikov 
Date:   2016-05-23T21:07:05Z

ignite-2620 Fixed entry expiration handling
(cherry picked from commit 46892c7)

commit 54e432e9bb6927351ea45d85b94965925a8351c7
Author: sboikov 
Date:   2016-05-23T18:08:14Z

ignite-2899 Fixed issues with 'keepBinary' handling, added test.
(cherry picked from commit e47440d)

commit c8269da30a1d55f06531857c52d254268056e84e
Author: sboikov 
Date:   2016-05-24T08:14:03Z

ignite-2620: Need override 'unswap' for detached entry.
(cherry picked from commit f7b376b)

commit e1ec0dedab0221b53dd11f2854c8c88b2641d147
Author: sboikov 
Date:   2016-05-24T11:31:43Z

IGNITE-2865 Continuous query event passed to filter should be immutable for 
users. This closes #744.
(cherry picked from commit 046657b)

commit 727afc87dce6c26756b56620c2aaccc3a3d0117e
Author: Vladislav Pyatkov 
Date:   2016-05-25T05:29:00Z

IGNITE-2667: Allow to start caches in PRIVATE and ISOLATED deployment modes 
when BinaryMarshaller is used

commit 183620cd31095dcd92471927cccf8741e3b63ed7
Author: nikolay_tikhonov 
Date:   2016-05-25T06:47:14Z

IGNITE-3168 Added idle timeout property.

commit 30aa287b881d4f9dc3fd5eec9840eab8d9a20828
Author: sboikov 
Date:   2016-05-24T13:57:20Z

ignite-2620 Skip empty entries in GridCacheMapEntry.onTtlExpired
(cherry picked from commit 6fc274a)

commit e2db87bb1b6c71d7978af17e9f2005ba1c661ab4
Author: sboikov 
Date:   2016-05-25T07:06:43Z

Added trace logging for entry/offheap updates.
(cherry picked from commit 9b2767f)

commit 6fcc7a41d8676956983792717483318b85781479
Author: MaBiao 
Date:   2016-05-25T09:54:40Z

IGNITE-2538 - IgniteRDD count() and isEmpty() method use IgniteCache API

commit e274d44a37fd1269e7a3a5fe1ee6139fd0b0
Author: Denis Magda 
Date:   2016-05-26T11:57:52Z

IGNITE-3188: Binary marshaller doesn't unmarshal a void type (added tests)

commit 6687e2bfb9627ce08c1c258527e2927606a500ed
Author: Yakov Zhdanov 
Date:   2016-05-13T08:48:00Z

review IGNITE-2708 Need to validate that SPIs are started only once
(cherry picked from commit cd063da)

commit 40a41fc50bdb73d50e2aa13da8203784be98e38a
Author: Yakov Zhdanov 
Date:   2016-05-13T08:59:02Z

reverting review IGNITE-2708 Need to validate that SPIs are started only 
once
(cherry picked from commit bf561e1)

commit d05786d8bfc8177223b6db9a98bd3c8170b6bcf1
Author: Ryan Zhao 
Date:   2016-05-13T09:00:43Z

review IGNITE-2708 Need to validate that SPIs are started only once (commit 
with proper author)
(cherry picked from commit 98338ff)

commit 9d937ca34775f39b46568eb3fca4585ce00a0fb1
Author: Yakov Zhdanov 
Date:   2016-05-13T09:54:01Z

review IGNITE-2708 Need to validate that SPIs are started only once (added 
logic to protect properly started grids)
(cherry picked from commit b8d624a)

commit 

[jira] [Created] (IGNITE-3780) [IGNITE-3764] ODBC: Support and test implicit functions (>, <, _, +, -, etc.).

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-3780:


 Summary: [IGNITE-3764] ODBC: Support and test implicit functions 
(>, <, _, +, -, etc.).
 Key: IGNITE-3780
 URL: https://issues.apache.org/jira/browse/IGNITE-3780
 Project: Ignite
  Issue Type: Task
  Components: odbc
Reporter: Vladimir Ozerov


The following functions must be supported and tested with all supported data 
types:
!=
%
+
- 
/
<
<=
==
> 
>= 




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

[jira] [Created] (IGNITE-3779) [IGNITE-3762] ODBC: Add tests for SQL_SQL92_RELATIONAL_JOIN_OPERATORS.

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-3779:


 Summary: [IGNITE-3762] ODBC: Add tests for 
SQL_SQL92_RELATIONAL_JOIN_OPERATORS. 
 Key: IGNITE-3779
 URL: https://issues.apache.org/jira/browse/IGNITE-3779
 Project: Ignite
  Issue Type: Task
  Components: odbc
Reporter: Vladimir Ozerov


We need to ensure that all SQL_AGGREGATE_FUNCTIONS [1] are really supported. 
Let's add tests for all mentioned functions.

SQL_SRJO_CORRESPONDING_CLAUSE (Intermediate level)
SQL_SRJO_CROSS_JOIN (Full level)
SQL_SRJO_EXCEPT_JOIN (Intermediate level)
SQL_SRJO_FULL_OUTER_JOIN (Intermediate level) 
SQL_SRJO_INNER_JOIN (FIPS Transitional level)
SQL_SRJO_INTERSECT_JOIN (Intermediate level)
SQL_SRJO_LEFT_OUTER_JOIN (FIPS Transitional level)
SQL_SRJO_NATURAL_JOIN (FIPS Transitional level)
SQL_SRJO_RIGHT_OUTER_JOIN (FIPS Transitional level)
SQL_SRJO_UNION_JOIN (Full level)

[1] https://msdn.microsoft.com/en-us/library/ms711681(v=vs.85).aspx#Anchor_16



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

[jira] [Created] (IGNITE-3781) [IGNITE-3765] ODBC: Get rid of Tableau warnings about unsupported aggregations.

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-3781:


 Summary: [IGNITE-3765] ODBC: Get rid of Tableau warnings about 
unsupported aggregations.
 Key: IGNITE-3781
 URL: https://issues.apache.org/jira/browse/IGNITE-3781
 Project: Ignite
  Issue Type: Task
  Components: odbc
Reporter: Vladimir Ozerov


Currently Tableau prints the following warning about our ODBC driver: 

{code}
This aggregation is unsupported: 'M/D/YY'
This aggregation is unsupported: ' '
This aggregation is unsupported: Attribute
This aggregation is unsupported: Day
This aggregation is unsupported: Hour
This aggregation is unsupported: Minute
This aggregation is unsupported: Month
This aggregation is unsupported: Quarter
This aggregation is unsupported: Second
This aggregation is unsupported: Std. Dev
This aggregation is unsupported: Std. Dev (Pop.)
This aggregation is unsupported: Trunc Day
This aggregation is unsupported: Trunc Hour
This aggregation is unsupported: Trunc Minute
This aggregation is unsupported: Trunc Month
This aggregation is unsupported: Trunc Quarter
This aggregation is unsupported: Trunc Second
This aggregation is unsupported: Trunc Week Number
This aggregation is unsupported: Trunc Year
This aggregation is unsupported: Variance
This aggregation is unsupported: Variance (Pop.)
This aggregation is unsupported: Week Number
This aggregation is unsupported: Weekday
This aggregation is unsupported: Year
{code}

We need to investigate what causes this and fix the root cause.



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

[jira] [Created] (IGNITE-3786) [IGNITE-3758] ODBC: Add tests for SQL_SQL92_DATETIME_FUNCTIONS.

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-3786:


 Summary: [IGNITE-3758] ODBC: Add tests for 
SQL_SQL92_DATETIME_FUNCTIONS.
 Key: IGNITE-3786
 URL: https://issues.apache.org/jira/browse/IGNITE-3786
 Project: Ignite
  Issue Type: Task
  Components: odbc
Reporter: Vladimir Ozerov
Priority: Minor


Let's add tests for SQL_SQL92_DATETIME_FUNCTIONS [1]

Affected functions:
SQL_SDF_CURRENT_DATE
SQL_SDF_CURRENT_TIME
SQL_SDF_CURRENT_TIMESTAMP

[1] https://msdn.microsoft.com/en-us/library/ms711681(v=vs.85).aspx#Anchor_16



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

[jira] [Created] (IGNITE-3787) [IGNITE-3759] ODBC: Add tests for SQL_DATETIME_LITERALS.

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-3787:


 Summary: [IGNITE-3759] ODBC: Add tests for SQL_DATETIME_LITERALS.
 Key: IGNITE-3787
 URL: https://issues.apache.org/jira/browse/IGNITE-3787
 Project: Ignite
  Issue Type: Task
  Components: odbc
Reporter: Vladimir Ozerov
Priority: Minor


Let's add tests for SQL_DATETIME_LITERALS [1]

Affected functions:
SQL_DL_SQL92_DATE
SQL_DL_SQL92_TIME
SQL_DL_SQL92_TIMESTAMP
SQL_DL_SQL92_INTERVAL_YEAR
SQL_DL_SQL92_INTERVAL_MONTH
SQL_DL_SQL92_INTERVAL_DAY
SQL_DL_SQL92_INTERVAL_HOUR
SQL_DL_SQL92_INTERVAL_MINUTE
SQL_DL_SQL92_INTERVAL_SECOND
SQL_DL_SQL92_INTERVAL_YEAR_TO_MONTH
SQL_DL_SQL92_INTERVAL_DAY_TO_HOUR
SQL_DL_SQL92_INTERVAL_DAY_TO_MINUTE
SQL_DL_SQL92_INTERVAL_DAY_TO_SECOND
SQL_DL_SQL92_INTERVAL_HOUR_TO_MINUTE
SQL_DL_SQL92_INTERVAL_HOUR_TO_SECOND
SQL_DL_SQL92_INTERVAL_MINUTE_TO_SECOND

[1] https://msdn.microsoft.com/en-us/library/ms711681(v=vs.85).aspx#Anchor_16



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

[jira] [Created] (IGNITE-3778) [IGNITE-3761] ODBC: Add tests for SQL_SQL92_VALUE_EXPRESSIONS.

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-3778:


 Summary: [IGNITE-3761] ODBC: Add tests for 
SQL_SQL92_VALUE_EXPRESSIONS. 
 Key: IGNITE-3778
 URL: https://issues.apache.org/jira/browse/IGNITE-3778
 Project: Ignite
  Issue Type: Task
  Components: odbc
Reporter: Vladimir Ozerov


We need to ensure that all SQL_SQL92_VALUE_EXPRESSIONS[1] are really supported. 
Let's add tests for all mentioned functions.

SQL_SVE_CASE
SQL_SVE_CAST
SQL_SVE_COALESCE
SQL_SVE_NULLIF

[1] https://msdn.microsoft.com/en-us/library/ms711681(v=vs.85).aspx#Anchor_16



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

[jira] [Created] (IGNITE-3784) [IGNITE-3767] Web Console: create reusable dialog for node selection

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-3784:


 Summary: [IGNITE-3767] Web Console: create reusable dialog for 
node selection
 Key: IGNITE-3784
 URL: https://issues.apache.org/jira/browse/IGNITE-3784
 Project: Ignite
  Issue Type: Task
  Components: wizards
Reporter: Alexey Kuznetsov


In several places (for example on SQL screen) we need to select some node where 
some task will be executed.

We need a reusable dialog that will display all nodes and will allow to select 
only one and return that node to calling code.



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

Re: Request for assign to ticket.

[Eduard Yuzlikeev]

Alexey,

Actually I think about next steps to solve problem:

1. Add method IgniteUtils#isCgroupsLimited which will detect JVM inside
container (dockerl, lxc, etc);

2. Call IgniteUtils#isCgroupsLimited inside
GridLocalMetrics#getAvailableProcessors
and detect available CPUs by calling "nproc" in cases when container was
detected;

3. Replace all calls of Runtime#getAvailableProcessors with
GridLocalMetrics#getAvailableProcessors;

What is the reason to create a new utility class like IgniteRuntimeUtils?

On Aug 26, 2016 2:21 PM, "Alexey Kuznetsov"  wrote:

> Eduard,
>
> I think if it is known bug it should be properly fixed by creating some
> utility class (for example, IgniteRuntimeUtils) that could be used all over
> Ignite code base.
> I do not think it is a good idea to "this #getRuntime calls with using
> GridLocalMetrics".
>
>
> On Fri, Aug 26, 2016 at 5:42 PM, Eduard Yuzlikeev <
> sinhrofazatron...@gmail.com> wrote:
>
> > Hi
> > I want to work on next bug
> > https://issues.apache.org/jira/browse/IGNITE-2092?jql=
> > project%20%3D%20IGNITE%20AND%20labels%20in%20%28newbie%29%
> > 20and%20status%20%3D%20OPEN
> > Can somebody assign me on it?
> >
> > I've investigated this issue and looks like this bug is on JVM side and
> > OpenJDK community fixed it only in Java 9 [1].
> > It's can be fixed fast inside GridLocalMetrics#getAvailableProcessors
> but
> > looks like other modules don't use it and detect available CPUs by
> calling
> > Runtime.getRuntime().*availableProcessors* [2].
> > Should I also replace this #getRuntime calls with using GridLocalMetrics?
> >
> > [1] https://bugs.openjdk.java.net/browse/JDK-8140793
> > [2]
> > https://github.com/apache/ignite/search?p=4=
> > availableProcessors=Code=%E2%9C%93
> > --
> > Best regards, Eduard Y.
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

[GitHub] ignite pull request #992: IGNITE-2946: Implemented query result fetching in ...

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-2946: Implemented query result fetching in batches.



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

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

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

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


commit 4e9e7b8ee1c990bacdc2d081b706ca315927fdce
Author: vozerov-gridgain 
Date:   2016-08-24T09:12:00Z

IGNITE-3716: ODBC: Added SQL escape sequence parsing.

commit 118db2fcffe3534aa1e5f4b97b8fbe23891752c4
Author: vozerov-gridgain 
Date:   2016-08-24T09:12:24Z

Merge remote-tracking branch 'upstream/ignite-1.6.6' into ignite-1.6.6

commit c02ad87f863bd730e60fb7052547fa0848e7eb77
Author: isapego 
Date:   2016-08-24T14:21:48Z

IGNITE-3736: ODBC: Added support for string scalar functions. This closes 
#979.

commit 13dfcbe03aca137ee70698f6083df27c10ecdaf9
Author: vozerov-gridgain 
Date:   2016-08-24T14:31:38Z

IGNITE-3736: ODBC: Reverted back removed "supported" futures.

commit d6449ffbc65acda6a2cf4484608188367837dd17
Author: sboikov 
Date:   2016-08-24T15:34:02Z

Fixed issues on node stop:
- in service processor need guard depExe access with busyLock
- do not error log IO errors in ClientImpl on stop

commit 5a3b3e2c6ecb5d6c96513b79f21828526b4a98a0
Author: isapego 
Date:   2016-08-25T09:35:07Z

IGNITE-3749: ODBC: Added support for numeric scalar functions. This closes 
#981.

commit 0e3a6e2df8b42f255a5a4688d5827dccaabfd3a4
Author: isapego 
Date:   2016-08-25T11:34:31Z

IGNITE-3757: ODBC: Added aggregate functions support. This closes #983.

commit e2f287039011bc9437c94fb574e61e2ac226
Author: Andrey V. Mashenkov 
Date:   2016-08-25T13:26:02Z

IGNITE-3738: ODBC: Fixed escape sequence whitespaces handling. This closes 
#982.

commit 8aabd6ea65d883d3bbcf37c05c146105dff8a6e2
Author: isapego 
Date:   2016-08-25T13:30:20Z

IGNITE-3751: ODBC: Added system functions support. This closes #985.

commit ae0b5ebf02f3eb70d24dd3b0eb63dde9843c82b0
Author: Andrey V. Mashenkov 
Date:   2016-08-26T08:12:31Z

IGNITE-3739: ODBC: Added GUID escape sequence support. This closes #988.

commit 6fd53ea5b50148e5a1156d83ea28acb8faf84035
Author: Igor Sapego 
Date:   2016-08-26T08:19:39Z

IGNITE-3761: ODBC: Added tests for SQL_SQL92_VALUE_EXPRESSIONS. This closes 
#989.

commit 99e3e8a2d997aa681264460c2845984712ded90e
Author: Igor Sapego 
Date:   2016-08-26T08:23:49Z

IGNITE-3764: ODBC Added tests for SQL operators. This closes #986.

commit 1a7f5adb0aee3f306b198b17dc8a29f6cd4850ca
Author: isapego 
Date:   2016-08-26T11:44:20Z

IGNITE-2946: Implemented query result fetching in batches.




---
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: Request for assign to ticket.

[Alexey Kuznetsov]

Eduard,

I think if it is known bug it should be properly fixed by creating some
utility class (for example, IgniteRuntimeUtils) that could be used all over
Ignite code base.
I do not think it is a good idea to "this #getRuntime calls with using
GridLocalMetrics".


On Fri, Aug 26, 2016 at 5:42 PM, Eduard Yuzlikeev <
sinhrofazatron...@gmail.com> wrote:

> Hi
> I want to work on next bug
> https://issues.apache.org/jira/browse/IGNITE-2092?jql=
> project%20%3D%20IGNITE%20AND%20labels%20in%20%28newbie%29%
> 20and%20status%20%3D%20OPEN
> Can somebody assign me on it?
>
> I've investigated this issue and looks like this bug is on JVM side and
> OpenJDK community fixed it only in Java 9 [1].
> It's can be fixed fast inside GridLocalMetrics#getAvailableProcessors but
> looks like other modules don't use it and detect available CPUs by calling
> Runtime.getRuntime().*availableProcessors* [2].
> Should I also replace this #getRuntime calls with using GridLocalMetrics?
>
> [1] https://bugs.openjdk.java.net/browse/JDK-8140793
> [2]
> https://github.com/apache/ignite/search?p=4=
> availableProcessors=Code=%E2%9C%93
> --
> Best regards, Eduard Y.
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[GitHub] ignite pull request #991: Ignite 3745

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

Ignite 3745



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

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

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

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


commit b5f594124dbdc75525bdd2c92fc49b9e126e60ab
Author: ashutak 
Date:   2016-05-18T17:47:26Z

ignite-3056: Service implementation class is required even if it's not 
expected to be deployed on current node (fixed)

commit c9416ed9b58bbb2287e896cc5860177939c4b3ed
Author: nikolay_tikhonov 
Date:   2016-05-20T09:54:55Z

Fixed IGNITE-3004 "Implement config variations test for ContinuousQueries"

commit 1ebbd57b74eef1abeb99fa9427667da17db9d01a
Author: sboikov 
Date:   2016-05-23T06:52:43Z

ignite-2528 Removed cache blocking operations from kernal write lock.

This closes #730
(cherry picked from commit f83a5f7)

commit 40a27e714d0bf62a26a35c90c68a020dbf0256c7
Author: sboikov 
Date:   2016-05-23T04:28:55Z

IGNITE-3175 BigDecimal fields are not supported if query is executed from 
IgniteRDD
(cherry picked from commit f2b390a)

commit 8e49e7013ea378c3040e1aa2d9494196d0833e40
Author: sboikov 
Date:   2016-05-23T16:42:45Z

ignite-2899 Fixed issues with 'keepBinary' handling. This closes #593.
(cherry picked from commit ee7e2c7)

commit 07611bd19beaf73a54f0627a6d8a71c3a1a09874
Author: sboikov 
Date:   2016-05-23T21:07:05Z

ignite-2620 Fixed entry expiration handling
(cherry picked from commit 46892c7)

commit 54e432e9bb6927351ea45d85b94965925a8351c7
Author: sboikov 
Date:   2016-05-23T18:08:14Z

ignite-2899 Fixed issues with 'keepBinary' handling, added test.
(cherry picked from commit e47440d)

commit c8269da30a1d55f06531857c52d254268056e84e
Author: sboikov 
Date:   2016-05-24T08:14:03Z

ignite-2620: Need override 'unswap' for detached entry.
(cherry picked from commit f7b376b)

commit e1ec0dedab0221b53dd11f2854c8c88b2641d147
Author: sboikov 
Date:   2016-05-24T11:31:43Z

IGNITE-2865 Continuous query event passed to filter should be immutable for 
users. This closes #744.
(cherry picked from commit 046657b)

commit 727afc87dce6c26756b56620c2aaccc3a3d0117e
Author: Vladislav Pyatkov 
Date:   2016-05-25T05:29:00Z

IGNITE-2667: Allow to start caches in PRIVATE and ISOLATED deployment modes 
when BinaryMarshaller is used

commit 183620cd31095dcd92471927cccf8741e3b63ed7
Author: nikolay_tikhonov 
Date:   2016-05-25T06:47:14Z

IGNITE-3168 Added idle timeout property.

commit 30aa287b881d4f9dc3fd5eec9840eab8d9a20828
Author: sboikov 
Date:   2016-05-24T13:57:20Z

ignite-2620 Skip empty entries in GridCacheMapEntry.onTtlExpired
(cherry picked from commit 6fc274a)

commit e2db87bb1b6c71d7978af17e9f2005ba1c661ab4
Author: sboikov 
Date:   2016-05-25T07:06:43Z

Added trace logging for entry/offheap updates.
(cherry picked from commit 9b2767f)

commit 6fcc7a41d8676956983792717483318b85781479
Author: MaBiao 
Date:   2016-05-25T09:54:40Z

IGNITE-2538 - IgniteRDD count() and isEmpty() method use IgniteCache API

commit e274d44a37fd1269e7a3a5fe1ee6139fd0b0
Author: Denis Magda 
Date:   2016-05-26T11:57:52Z

IGNITE-3188: Binary marshaller doesn't unmarshal a void type (added tests)

commit 6687e2bfb9627ce08c1c258527e2927606a500ed
Author: Yakov Zhdanov 
Date:   2016-05-13T08:48:00Z

review IGNITE-2708 Need to validate that SPIs are started only once
(cherry picked from commit cd063da)

commit 40a41fc50bdb73d50e2aa13da8203784be98e38a
Author: Yakov Zhdanov 
Date:   2016-05-13T08:59:02Z

reverting review IGNITE-2708 Need to validate that SPIs are started only 
once
(cherry picked from commit bf561e1)

commit d05786d8bfc8177223b6db9a98bd3c8170b6bcf1
Author: Ryan Zhao 
Date:   2016-05-13T09:00:43Z

review IGNITE-2708 Need to validate that SPIs are started only once (commit 
with proper author)
(cherry picked from commit 98338ff)

commit 9d937ca34775f39b46568eb3fca4585ce00a0fb1
Author: Yakov Zhdanov 
Date:   2016-05-13T09:54:01Z

review IGNITE-2708 Need to validate that SPIs are started only once (added 
logic to protect properly started grids)
(cherry picked from commit b8d624a)

commit edc2947d7340cac4a3c90fa726c23d5d47798ab9
Author: vozerov-gridgain 

Re: Request for assign to ticket.

[Sergi Vladykin]

I've added you to contributors list in Jira, feel free to assign the issue
to yourself.

Sergi

2016-08-26 13:42 GMT+03:00 Eduard Yuzlikeev :

> Hi
> I want to work on next bug
> https://issues.apache.org/jira/browse/IGNITE-2092?jql=
> project%20%3D%20IGNITE%20AND%20labels%20in%20%28newbie%29%
> 20and%20status%20%3D%20OPEN
> Can somebody assign me on it?
>
> I've investigated this issue and looks like this bug is on JVM side and
> OpenJDK community fixed it only in Java 9 [1].
> It's can be fixed fast inside GridLocalMetrics#getAvailableProcessors but
> looks like other modules don't use it and detect available CPUs by calling
> Runtime.getRuntime().*availableProcessors* [2].
> Should I also replace this #getRuntime calls with using GridLocalMetrics?
>
> [1] https://bugs.openjdk.java.net/browse/JDK-8140793
> [2]
> https://github.com/apache/ignite/search?p=4=
> availableProcessors=Code=%E2%9C%93
> --
> Best regards, Eduard Y.
>

[jira] [Created] (IGNITE-3774) Web Console: Move ACL checks to AuthService

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3774:


 Summary: Web Console: Move ACL checks to AuthService
 Key: IGNITE-3774
 URL: https://issues.apache.org/jira/browse/IGNITE-3774
 Project: Ignite
  Issue Type: Task
  Components: wizards
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
 Fix For: 1.8


Move ACL checks to AuthService for better testing and clean architecture.



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