[jira] [Created] (IGNITE-8900) SqlFieldsQuery provides incorrect result when item size exceeds page size

2018-06-29 Thread Anton Kurbanov (JIRA)
Anton Kurbanov created IGNITE-8900: -- Summary: SqlFieldsQuery provides incorrect result when item size exceeds page size Key: IGNITE-8900 URL: https://issues.apache.org/jira/browse/IGNITE-8900

[jira] [Created] (IGNITE-8901) Duplicate messages in TcpCommunicationSpi result in "Cache is restarting" messages

2018-06-29 Thread Andrew Medvedev (JIRA)
Andrew Medvedev created IGNITE-8901: --- Summary: Duplicate messages in TcpCommunicationSpi result in "Cache is restarting" messages Key: IGNITE-8901 URL: https://issues.apache.org/jira/browse/IGNITE-8901

[GitHub] ignite pull request #4285: Ignite 8747 fresh

2018-06-29 Thread glukos
GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/4285 Ignite 8747 fresh You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8747-fresh Alternatively you can review and

is these correct?

2018-06-29 Thread kcheng.mvp
here is the environment : 1 server node + 1 client node executed below code === IgniteCache igniteCache = igniteSpringBean.getOrCreateCache("HappyFlow"); igniteCache.put("hello", "hello1"); Assert.assertEquals("hello1",igniteCache.get("hello"));

Re: Please Subscribe me

2018-06-29 Thread kcheng.mvp
Thank you very much! I can see my post now. by the way, can you take a look about my question? http://apache-ignite-developers.2346864.n4.nabble.com/is-these-correct-td32111.html -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-8896) Wrong javadoc for TcpCommunicationSpi.setSlowClientQueueLimit()

2018-06-29 Thread Dmitry Karachentsev (JIRA)
Dmitry Karachentsev created IGNITE-8896: --- Summary: Wrong javadoc for TcpCommunicationSpi.setSlowClientQueueLimit() Key: IGNITE-8896 URL: https://issues.apache.org/jira/browse/IGNITE-8896

[jira] [Created] (IGNITE-8897) Node with longer BaselineHistory joining the cluster causes cluster stopping

2018-06-29 Thread Sergey Chugunov (JIRA)
Sergey Chugunov created IGNITE-8897: --- Summary: Node with longer BaselineHistory joining the cluster causes cluster stopping Key: IGNITE-8897 URL: https://issues.apache.org/jira/browse/IGNITE-8897

Potential OOM while iterating over query cursor. Review needed.

2018-06-29 Thread Andrey Mashenkov
Hi Igniters, There is an issue IGNITE-8892 [1] related to OOM during distributed query execution. This issue is not limited with ScanQuery usage and looks like affected all query types. The use case is quite simple. 1 server and 1 client. Client starts scan query with default flags and iterate

[jira] [Created] (IGNITE-8899) IgniteJdbcDriver directly create JavaLogger in static context

2018-06-29 Thread Evgenii Zhuravlev (JIRA)
Evgenii Zhuravlev created IGNITE-8899: - Summary: IgniteJdbcDriver directly create JavaLogger in static context Key: IGNITE-8899 URL: https://issues.apache.org/jira/browse/IGNITE-8899 Project:

[GitHub] ignite pull request #4247: IGNITE-8858 - Client none may not stop.

2018-06-29 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4247 ---

[GitHub] ignite pull request #4284: IGNITE-8899 remove creating JavaLogger in static ...

2018-06-29 Thread ezhuravl
GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/4284 IGNITE-8899 remove creating JavaLogger in static context in IgniteJdb… …cDriver You can merge this pull request into a Git repository by running: $ git pull

Re: Review IGNITE-8859

2018-06-29 Thread Petr Ivanov
Looks good. Did you intentionally not mentioned JDK10 in warning/error texts? Also have you tested running built Apache Ignite under JDK10? > On 29 Jun 2018, at 17:06, Dmitry Karachentsev > wrote: > > Forgot a link to the ticket https://issues.apache.org/jira/browse/IGNITE-8859 > >

[GitHub] ignite pull request #4249: IGNITE-8426 LongJVMPauseDetector add logger from ...

2018-06-29 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4249 ---

[GitHub] ignite pull request #4283: GG-13963

2018-06-29 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4283 GG-13963 rename command argument '--force' to '--yes' for control.sh You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Review IGNITE-8859

2018-06-29 Thread Petr Ivanov
Very nice! I’ll try to review changes at weekend. > On 29 Jun 2018, at 17:40, Dmitry Karachentsev > wrote: > > Hi Petr, > > Yes, as I said I tested on following JDKs: 1.7, 1.8, 9 and 10. > In waring showed JAVA_HOME directory. If it would be useful, I can add > detected version. > >

Re: Review IGNITE-8859

2018-06-29 Thread Dmitry Karachentsev
Hi Petr, Yes, as I said I tested on following JDKs: 1.7, 1.8, 9 and 10. In waring showed JAVA_HOME directory. If it would be useful, I can add detected version. Thanks! 29.06.2018 17:34, Petr Ivanov пишет: Looks good. Did you intentionally not mentioned JDK10 in warning/error texts? Also

[GitHub] ignite pull request #4282: IGNITE-7149: Gradient Boosting on Trees

2018-06-29 Thread avplatonov
GitHub user avplatonov opened a pull request: https://github.com/apache/ignite/pull/4282 IGNITE-7149: Gradient Boosting on Trees Implementation GDB on DecisionTrees You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-8898) rename command argument '--force' to '--yes' for control.sh

2018-06-29 Thread Max Shonichev (JIRA)
Max Shonichev created IGNITE-8898: - Summary: rename command argument '--force' to '--yes' for control.sh Key: IGNITE-8898 URL: https://issues.apache.org/jira/browse/IGNITE-8898 Project: Ignite

Please Subscribe me

2018-06-29 Thread Ken Cheng
Thanks, Ken Cheng

Access to change jira status

2018-06-29 Thread uday kale
Hi, I am unable to change the jira status of IGNITE-1260 or assign it to myself. Can someone grant me the necessary permissions. My jira user name is: uday. Regards, Uday

[GitHub] ignite pull request #4279: check ssh fix for TC flucky tests

2018-06-29 Thread 1vanan
GitHub user 1vanan opened a pull request: https://github.com/apache/ignite/pull/4279 check ssh fix for TC flucky tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/1vanan/ignite SshTests Alternatively you can review and

Re: Access to change jira status

2018-06-29 Thread Valentin Kulichenko
Hi Uday, I added you to contributors list, you should be able to assign the ticket to yourself now. Welcome to the community! -Val On Fri, Jun 29, 2018 at 3:40 AM uday kale wrote: > Hi, > > I am unable to change the jira status of IGNITE-1260 or assign it to > myself. Can someone grant me the

Re: Thin Client lib: Python

2018-06-29 Thread Dmitry Melnichuk
Hi, Dmitry! I guess there will be no IEP specifically for the client, because it has nothing to do with Ignite enhancing, as what IEP stands for. From Ignite side, the purpose and potential capabilities of the thin client, aka binary API client, is best described by this document:

[GitHub] ignite pull request #4268: IGNITE-5980 Failing testClientAtomicLongCreateClo...

2018-06-29 Thread 1vanan
Github user 1vanan closed the pull request at: https://github.com/apache/ignite/pull/4268 ---

[GitHub] ignite pull request #4280: exception when try to enable atomic operation in ...

2018-06-29 Thread SomeFire
GitHub user SomeFire opened a pull request: https://github.com/apache/ignite/pull/4280 exception when try to enable atomic operation in tx IGNITE-2313 Need to add a mode to fail atomic operations within a transaction You can merge this pull request into a Git repository by

Re: Access to change jira status

2018-06-29 Thread uday kale
Thanks Valentin On Fri, Jun 29, 2018 at 4:15 PM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Uday, > > I added you to contributors list, you should be able to assign the ticket > to yourself now. Welcome to the community! > > -Val > > On Fri, Jun 29, 2018 at 3:40 AM uday kale

Re: Please Subscribe me

2018-06-29 Thread Dmitriy Setrakyan
Ken, seems like you have subscribed. Generally, all you have to do is send an email to dev-subsci...@ignite.apache.org and then simply reply to the confirmation email. D. On Fri, Jun 29, 2018 at 5:01 AM, Ken Cheng wrote: > Thanks, > Ken Cheng >

[GitHub] ignite pull request #4281: IGNITE-8859 - Open upper Java verison bounds

2018-06-29 Thread dkarachentsev
GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/4281 IGNITE-8859 - Open upper Java verison bounds You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8859

Re: Thin Client lib: Python

2018-06-29 Thread Dmitry Melnichuk
Dmitry, I have mentioned Jira task in my reply earlier today. Sorry, but the task description was a bit messy and less than informative. I just updated it. Please have a look. https://issues.apache.org/jira/browse/IGNITE-7782 Please let me know if this information is supposed to be

Re: Review IGNITE-8859

2018-06-29 Thread Dmitry Karachentsev
Forgot a link to the ticket https://issues.apache.org/jira/browse/IGNITE-8859 29.06.2018 17:06, Dmitry Karachentsev пишет: Hi guys, I've enhanced our scripts a bit to allow run Ignite on Java 10+. Please review. I'm not sure if there exist tests, but I tested on Windows/Linux for 1.7,

Review IGNITE-8859

2018-06-29 Thread Dmitry Karachentsev
Hi guys, I've enhanced our scripts a bit to allow run Ignite on Java 10+. Please review. I'm not sure if there exist tests, but I tested on Windows/Linux for 1.7, 1.8, 9 and 10 JDKs manually. Thanks!