Re: Is it time to move forward to JUnit4 (5)?

A transition to junit5 should also be easy - even for the real junit5 (called Jupiter) and not the junit5 compatibility layer (called vintage). For Jupiter the major changes are the order of arguments for assertions (I came over this for 1000 test case with probably 1 assertions in another

Re: Problem with reading incomplete payload - IGNITE-7153

I have not checked the exact routine, but you need to reexecute read until it returns -1 or if known that all bytes that are expected have been read (if sockCh is based on some kind of input stream) > Am 26.10.2018 um 04:24 schrieb Michael Fong : > > Bump! > > Anyone who could help me solve

Re: Static code analysis for Java

Why do not use all of the tools (well at least several). They are easy to be integrateable. In this way one would be less exposed to promote one commercial vendor over the other. This would also help in finding the right quality criteria instead of analyzing what is offered by only one

Re: Spark Data Frame support in Ignite

he.org> wrote: > >> On Thu, Aug 3, 2017 at 8:45 AM, Jörn Franke <jornfra...@gmail.com> wrote: >> >> I think the JDBC one is more inefficient, slower requires too much >> development effort. You can also check the integration of Alluxio with >> Spark. >>

Re: Spark Data Frame support in Ignite

anks, > D. > >> On Thu, Aug 3, 2017 at 7:40 AM, Jörn Franke <jornfra...@gmail.com> wrote: >> >> These are two different things. Spark applications themselves do not use >> JDBC - it is more for non-spark applications to access Spark DataFrames. >> >> A

Re: Spark Data Frame support in Ignite

These are two different things. Spark applications themselves do not use JDBC - it is more for non-spark applications to access Spark DataFrames. A direct support by Ignite would make more sense. Although you have in theory IGFS, if the user is using HDFS, which might not be the case. It is now

Re: Compatible spark version for ignite

Looks like it cannot find the scala library and/or wrong scala version is available to the application. > On 23 Mar 2017, at 09:08, Purushotham Muthuluru wrote: > > Hi , > > I am using Spark 2.1.0 with Ignite v1.9 , I get following error when I try to > run a example, I do

Re: Rethink native SQL API in Apache Ignite 2.0

Keep in mind security, e.g. SQL injections. Ideally the API should be designed in such a way that the programmer cannot use it wrongly and allow sql injections. > On 7 Feb 2017, at 12:34, Vladimir Ozerov wrote: > > Igniters, > > Our SQL engine becomes more and more

Re: ignite-spark module in Hadoop Accelerator

You can cache often used hive tables/partitions (ideally using tez engine and orc format) since they are just files. However , it could be optimized that it automatically detects which tables/partitions are often used. This use case might become irrelevant with Hive LLAP. > On 19 Nov 2016, at

Re: Abandoned ticket: Provide Integration with Spring Data [IGNITE-1192]

Sent from my iPhone > On 16 Dec 2015, at 10:45, Denis Magda wrote: > > I've unassigned the ticket from Vikrant. > > Is anyone in the community is interesting in taking over this task? > > -- > Denis > >> On 12/15/2015 3:36 PM, Denis Magda wrote: >> Hi Vikrant, >> >>