+1
Aleksandr, thanks for the explanation.
Best regards,
Ivan Pavlukhin
чт, 26 мая 2022 г. в 21:54, Andrey Gura :
>
> +1 from me. Open API spec could be useful in the future for
> implementing external cluster management tools.
>
> On Thu, May 26, 2022 at 11:41 AM Aleksandr Pakhomov wrote:
> >
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
+1 from me. Open API spec could be useful in the future for
implementing external cluster management tools.
On Thu, May 26, 2022 at 11:41 AM Aleksandr Pakhomov wrote:
>
> Hi Ivan,
>
> Dependencies that are needed for annotating
> classes are going to be included. From those
> annotations Open
Hi Maksim.
Do I understand correctly that 'consistent cut start' message always
contains IDs of transactions to include, while 'consistent cut finish'
message always contains IDs of transactions to exclude from the
consistent cut? (At least, this is the impression I got from the
example of
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New Critical Failure in master Cache 6
https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=%3Cdefault%3E
No changes in the build
- Here's a
Hi Ivan,
Dependencies that are needed for annotating
classes are going to be included. From those
annotations Open API spec is generated by
maven plugin. That’s it.
If you are asking about swagger ui or any
web stuff then the answer is no. We are
not going to include this into production.
Hello Igniters.
I see that the main argument against Micronaut is that we need
Micronaut+Swagger to achieve IEP 87 if we can use only Swagger. I agree
this is a valid point and logically. But I think we can take a look into it
from another side, from future vision. Main idea to start using
