+1
чт, 20 июня 2019 г., 8:28 Павлухин Иван :
> +1
>
> чт, 20 июн. 2019 г. в 04:18, Valentin Kulichenko
> :
> >
> > +1
> >
> > On Wed, Jun 19, 2019 at 5:58 PM Roman Shtykh
> > wrote:
> >
> > > +1
> > >
> > >
> > > On Thursday, June 20, 2019, 7:34:47 a.m. GMT+9, Andrey Gura <
> > > ag...@apach
For curious ones I copied a RunAll DSL configuration to gist [1].
[1] https://gist.github.com/pavlukhin/e788bbebafe69ce9d9a3c9e9871ab8c4
чт, 20 июн. 2019 г. в 08:42, Павлухин Иван :
>
> Dmitriy,
>
> It is a very important topic for Ignite CI. I think it would be great
> if all significant changes
Dmitriy,
It is a very important topic for Ignite CI. I think it would be great
if all significant changes in a build configuration goes with a
meaningful description (a commit message). As for me, DSL sounds
promising.
BTW, a special rights are needed to view
https://ci.ignite.apache.org/admin/ed
+1
чт, 20 июн. 2019 г. в 04:18, Valentin Kulichenko
:
>
> +1
>
> On Wed, Jun 19, 2019 at 5:58 PM Roman Shtykh
> wrote:
>
> > +1
> >
> >
> > On Thursday, June 20, 2019, 7:34:47 a.m. GMT+9, Andrey Gura <
> > ag...@apache.org> wrote:
> >
> > +1
> >
> > On Thu, Jun 20, 2019 at 12:58 AM Denis Mag
+1
On Wed, Jun 19, 2019 at 5:58 PM Roman Shtykh
wrote:
> +1
>
>
> On Thursday, June 20, 2019, 7:34:47 a.m. GMT+9, Andrey Gura <
> ag...@apache.org> wrote:
>
> +1
>
> On Thu, Jun 20, 2019 at 12:58 AM Denis Magda wrote:
> >
> > Igniters,
> >
> > Based on our earlier discussion [1], let's for
+1
On Thursday, June 20, 2019, 7:34:47 a.m. GMT+9, Andrey Gura
wrote:
+1
On Thu, Jun 20, 2019 at 12:58 AM Denis Magda wrote:
>
> Igniters,
>
> Based on our earlier discussion [1], let's formalize our decision and vote
> for the following:
>
> - IGFS and In-Memory Hadoop Accelerat
+1
On Thu, Jun 20, 2019 at 12:58 AM Denis Magda wrote:
>
> Igniters,
>
> Based on our earlier discussion [1], let's formalize our decision and vote
> for the following:
>
>- IGFS and In-Memory Hadoop Accelerator components are to be
>discontinued and no longer supported by the community
>
Igniters,
Based on our earlier discussion [1], let's formalize our decision and vote
for the following:
- IGFS and In-Memory Hadoop Accelerator components are to be
discontinued and no longer supported by the community
- The existing source code of IGFS and In-Memory Hadoop Accelerator i
Pavel replied to me in private: encryption is available since 2.4 for .Net
thin client.
I've also modified source XML
https://github.com/apache/ignite/pull/6616/files#diff-1995c8a78832996cb48db91f7550479cR8
чт, 20 июн. 2019 г. в 00:10, Denis Magda :
> Pavel,
>
> I still have no info related to
Pavel,
I still have no info related to starting version of .NET encryption
> support. So I supposed it was 1.5.
Could you please help with this last open item?
Dmitry, thanks for the final summary. I'll contact ASF folks trying to find
the ASF website dev instructions.
--
Denis Magda
On Wed
Maxim,
Well, it is an interesting point. First of all I want to believe that
issues occurring only on a specific Java version are rare. If so,
running tests on a single version for a visa should be enough.
On the other hand, a uniform test environment sounds a good idea
(especially for a visa), p
Hi Denis,
I still have no info related to starting version of .NET encryption
support. So I supposed it was 1.5.
I've started both XSTLs and added an example of both XLTs output to google
doc tabs. One transformer is for email template generation (requires
project name), another is for the site t
Amelchev Nikita created IGNITE-11936:
Summary: Avoid changing AffinityTopologyVersion on a server node
join/left event from not baseline topology.
Key: IGNITE-11936
URL: https://issues.apache.org/jira/browse/I
Folks,
Maybe I'm missing something, but what is the reason for setting
JAVA_HOME randomly? For instance, some commit is working under jdk8
but fails under jdk9 (and we declare that 9-th version is supported by
Ignite). Should we merge this commit to the master branch (all test
suites can be OK und
Igniters,
as for older versions, I've started to collect information of crypto
providers usages in older versions, please help me to finalize this doc so
I could prepare a declaration of older versions.
https://docs.google.com/spreadsheets/d/1s15HnsE40hHl0QN2aX0hJ3atw9_LO19_mzhgM96rcbo/edit?usp=s
Hi Denis,
Build process seems to be mentioned only here
https://www.apache.org/dev/crypto.html#sources It also mentions some
bisnotice XSLT transformation, which is available at SVN here
https://svn.apache.org/repos/asf/infrastructure/site/trunk/content/licenses/exports/
For XML I'm preparing at
Dmitriy,
Thank you for the hint! Java version seems to be the reason. I see
that tests pass with Java 8 and 11 and fail with Java 10. See the
exception below. Btw, do we test with Java 9? Have not seen that
version in recent runs.
java.lang.NoClassDefFoundError: javax/transaction/SystemException
Denis,
Documentation for memory usage calculation covers another case (memory
usage by the node).
There is no ability (AFAIK) in released Ignite versions to calculate memory
used by a cache or cache group when persistence is disabled.
Dedicated data region can be used for some of the caches in som
18 matches
Mail list logo
