Ivan,
Indeed junit5 has a lot of powerful features which can improve testing process.
But first we should go through a migration process. There are several
items which looks quite challenging.
1. Test suites support. Correct me if I am missed it, but I have not
found a concept of test suites simi
Ivan Pavlukhin created IGNITE-11398:
---
Summary: Remove leftover @RunWith(JUnit4.class)
Key: IGNITE-11398
URL: https://issues.apache.org/jira/browse/IGNITE-11398
Project: Ignite
Issue Type: T
Vladimir,
Ok, agreed, let's not boil the ocean...at least for now ;)
--
Denis Magda
On Sat, Feb 23, 2019 at 12:50 AM Vladimir Ozerov
wrote:
> Denis,
>
> Yes, this is what my answer was about - you cannot have SQL without
> defining fields in advance. Because it breaks a lot of standard SQL
>
Igor, would you be able to help with the Cassandra support?
--
Denis Magda
On Sat, Feb 23, 2019 at 1:03 AM Roman Shtykh
wrote:
> Dmitriy, I will have a look at the Camel Streamer.
>
> -- Roman
>
>
> On Tuesday, February 19, 2019, 2:26:26 a.m. GMT+9, Dmitriy Pavlov <
> dpav...@apache.org> w
Uday Kale created IGNITE-11397:
--
Summary: Binary mode for Ignite Queue
Key: IGNITE-11397
URL: https://issues.apache.org/jira/browse/IGNITE-11397
Project: Ignite
Issue Type: New Feature
Dmitriy, I will have a look at the Camel Streamer.
-- Roman
On Tuesday, February 19, 2019, 2:26:26 a.m. GMT+9, Dmitriy Pavlov
wrote:
Hi Igniters,
I've noticed we have a couple more Java11 related failures: Tests here
didn't start at all, so assistance here for finding out
- reasons
Denis,
Yes, this is what my answer was about - you cannot have SQL without
defining fields in advance. Because it breaks a lot of standard SQL
invariants and virtually makes the whole language unusable. For instance,
think of product behavior in the following cases:
1) User queries an empty cache
Denis, thank you for ranging.
I am working on service hot-redeployment via DeploymentSpi [1]. This
allows us using the feature without changing public API.
[1] https://issues.apache.org/jira/browse/IGNITE-11384
On Thu, Feb 7, 2019 at 11:53 PM Denis Magda wrote:
>
> Vyacheslav,
>
> Such tasks ag
Pavel,
>> A new version of Ignite has released and a developer should update
>> compatibility tests to run it against the new version.
Now I think that understand a problem which you are trying to solve,
but I'd suggest another solution:
In unit-testing world such problems usually is solved simil
