Hi Igniters,
I've started the process of updating
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process and
merging other pages and sources into one single page.
The document is not final, I will add changes as soon as I do steps.
Feedback is, as always, welcomed!
Sincerely
Dmitriy
Hello!
Consider adding ;lazy=true to connection string. You're causing overly huge
result set to be held on heap otherwise.
Regards,
--
Ilya Kasnacheev
пт, 7 июн. 2019 г. в 19:07, Shane Duan :
> Thanks Denis.
>
> Oops, copied wrong section of log file. The previous log which complains
> schem
Thanks Denis.
Oops, copied wrong section of log file. The previous log which complains
schema will happen for any further operations once Ignite crashed.
Here is how I prepared the JDBC connection:
String connectionStr = "jdbc:ignite:thin://" + hostName + ":" + portNumber +";"
+ "schema=" +
Nikolay,
+1.
I'd add my 50 cents.
There should no TODOs without any ticket link, otherwise such TODOs will
never be fixed.
On Fri, Jun 7, 2019 at 4:23 PM Andrey Gura wrote:
> Big +1 from me.
> Make code base clean and clear.
>
> On Fri, Jun 7, 2019 at 3:26 PM Nikolay Izhikov
> wrote:
> >
> > H
Maxim Muzafarov created IGNITE-11903:
Summary: Checkstyle must support to JavadocStyle rule
Key: IGNITE-11903
URL: https://issues.apache.org/jira/browse/IGNITE-11903
Project: Ignite
Issue
Maxim Muzafarov created IGNITE-11904:
Summary: Checkstyle must support JavadocVariable rule
Key: IGNITE-11904
URL: https://issues.apache.org/jira/browse/IGNITE-11904
Project: Ignite
Issue
Maxim Muzafarov created IGNITE-11902:
Summary: Checkstyle must support MagicNumbers rule
Key: IGNITE-11902
URL: https://issues.apache.org/jira/browse/IGNITE-11902
Project: Ignite
Issue Ty
Ivan Pavlukhin created IGNITE-11901:
---
Summary: CacheMvccTransactionsTest.testMvccCoordinatorChangeSimple
is flaky
Key: IGNITE-11901
URL: https://issues.apache.org/jira/browse/IGNITE-11901
Project: I
Big +1 from me.
Make code base clean and clear.
On Fri, Jun 7, 2019 at 3:26 PM Nikolay Izhikov wrote:
>
> Hello, Igniters.
>
> Please, pay attention to commits quality.
>
> 1. Please, writer Javadocs.
> 2. Please, make the new lines according to code style.
>
> Issues like [1] has to be fixed *BE
Denis Chudov created IGNITE-11900:
-
Summary: Fix ClassPathContentLoggingTest test
Key: IGNITE-11900
URL: https://issues.apache.org/jira/browse/IGNITE-11900
Project: Ignite
Issue Type: Bug
Hello, Petr.
> at least Scala does not compile
How cat I reproduce it?
Do we have ticket?
В Пт, 07/06/2019 в 15:28 +0300, Petr Ivanov пишет:
> Suite fails because Apache Ignite compilation is not supported under JDK 9+
> (at least Scala does not compile).
> Your build from [3] was triggered wit
Petr,
Yes, I see thanks. How can we force the suite to use the only JDK8?
I see the configuration parameter: JDK home path: %env.JDK_ORA_18%,
but probably it works not well enough.
On Fri, 7 Jun 2019 at 15:28, Petr Ivanov wrote:
>
> Suite fails because Apache Ignite compilation is not supported
Suite fails because Apache Ignite compilation is not supported under JDK 9+ (at
least Scala does not compile).
Your build from [3] was triggered with JDK 11.
> On 7 Jun 2019, at 14:57, Maxim Muzafarov wrote:
>
> Igniters,
>
> I've noticed a few problems with Code Style Check Suite on TC in the
Hello, Igniters.
Please, pay attention to commits quality.
1. Please, writer Javadocs.
2. Please, make the new lines according to code style.
Issues like [1] has to be fixed *BEFORE* commit.
[1]
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/interna
Igniters,
I've noticed a few problems with Code Style Check Suite on TC in the
master branch.
1. Some of the rules have been violated by previous commits to the
master branch. I've created ticket [1] and have prepared PR [2] which
is fixing it.
Dmitry, or maybe someone else, can you take a look,
Maxim Muzafarov created IGNITE-11899:
Summary: Fix code style violation
Key: IGNITE-11899
URL: https://issues.apache.org/jira/browse/IGNITE-11899
Project: Ignite
Issue Type: Bug
Vyacheslav,
> Ivan, according to described issues with versions it looks like some
> previously built artefacts have been cashed in Maven local repository.
Versions I saw actually are consistent with a way how they had been
built. But they look a little bit surprising. But actually I do not
know
+1 from me. Built from sources and run several examples.
On Fri, Jun 7, 2019 at 2:52 AM Yuriy Babak wrote:
>
> +1 - checked ML examples
>
> Best regards,
> Yuriy Babak
>
>
> чт, 6 июн. 2019 г. в 19:16, Павлухин Иван :
>
> > +1
> > Launched a couple of nodes using bin package. Run SQL examples
> >
Dmitry, thank you for pointing this out, I just mixed threads.
>> 3. Some mix of versions reported by nodes launched in different ways.
Ivan, according to described issues with versions it looks like some
previously built artefacts have been cashed in Maven local repository.
On Fri, Jun 7, 2019 a
19 matches
Mail list logo
