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 p
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 th
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 solution
On Thu, Aug 3, 2017 at 8:45 AM, Jörn Franke 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.
>>
>
> As far as I know, Alluxio is a file syste
.
Alternatively for inserting / updating single rows.
> On 3. Aug 2017, at 08:17, Dmitriy Setrakyan wrote:
>
> Jorn, thanks for your feedback!
>
> Can you explain how the direct support would be different from the JDBC
> support?
>
> Thanks,
> D.
>
>>
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
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 not have scala inst
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 sophisticated. Initially we
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
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,
>>
>> Do you have free time t
10 matches
Mail list logo
