Created issues related building ODBC module, running C++ suites and
removing VS project files
1. https://issues.apache.org/jira/browse/IGNITE-15637
2.https://issues.apache.org/jira/browse/IGNITE-15636
вс, 26 сент. 2021 г. в 19:50, Ivan Daschinsky :
> +1
>
> Let's consider building odbc driver us
Hello!
If we go the second route, we can call the field "Generation".
Generation: Ignite 2.x
Generation: Ignite 3
(no new tickets should ever be filed for Ignite 1.x but if they are, they
should go to the first Generation)
Regards.
--
Ilya Kasnacheev
ср, 29 сент. 2021 г. в 00:33, Valentin Ku
Hello, Valentin.
> Nikolay, Ilya, Denis, and others who opposed the initial suggestion
It seems I don’t write my point clear.
I’m +1 to have another jira project for Ignite3.
My point is - Ignite3 is not Ignite - it just another database engine.
> Ignite 2 and Ignite 3 are *technically* separat
> I believe that we should improve Ignite evolutionary and not revolutionary.
> First of all, change user API with the slow improvements step by step.
Nikolay,
Does you vision of evolutionary improvement involve technical debt addressing?
>
>
>> 29 сент. 2021 г., в 11:43, Ilya Kasnacheev
> Does you vision of evolutionary improvement involve technical debt addressing
Yes, of course.
My vision was the following (from the bird eye):
- 2.20 - removals of LOCAL caches, MVCC and other abandoned features. (User API
doesn’t change).
- 2.30 - replace static XML configuration with the ne
And what about:
— issues related to Maven build? possible Gradle upgrade?
— issues related to run scripts?
— issues related to release and delivery processes and scripts?
Are they going to be addressed during Apache Ignite evolution too?
> On 29 Sep 2021, at 13:47, Nikolay Izhikov wrote:
>
>
> — issues related to Maven build? possible Gradle upgrade?
I’m not aware of the issues.
Can you, please, send a tickets or description of existing issues?
Anyway, it seems change of build tool can be done at any time we want
> — issues related to run scripts?
> — issues related to release and de
I am watching how Apache Ignite does evolve for over a 3 years already and see
that such hidden (almost no Open Source Community points could be achieved for
refactoring and addressing something that is not directly project's source
executable code) issues drown under constant pressure of new fe
A new feedback has been added, go to bugyard.io to see all the details...
https://bugyard.io
A new feedback has been added
"https://ignite.apache.org/docs/latest/SQL/sql-api#inserting-updating-deleting-and-merging
why there are no .net instance?" by fatihcandan52
View feedback
https://app
Hi Pavel,
Thanks for the direction.
I created the account and have run the TCBot build and added the comment to
the Jira ticket.
There seem to be a lot of failing tests, though I suspect they are mostly
flapping/unstable tests rather than failures due to the change in the PR,
but the TCBot build
Hi Ilya!
Currently we respond to users via the Bugyard.io reply form, which does not
support putting others on CC.
Nevertheless all the conversations are saved in Bugyard and can be reached
by all the Igniters.
Regarding our previous discussion:
As I mentioned before, I'm taking the first shift
11 matches
Mail list logo
