Sergey Kozlov created IGNITE-11501:
--
Summary: Build examples failed with Scala profile and Java11
Key: IGNITE-11501
URL: https://issues.apache.org/jira/browse/IGNITE-11501
Project: Ignite
Is
Nikolai Svistov created IGNITE-11502:
Summary: Django engine
Key: IGNITE-11502
URL: https://issues.apache.org/jira/browse/IGNITE-11502
Project: Ignite
Issue Type: New Feature
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 finalize
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 finalize
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 finalize
Ivan Pavlukhin created IGNITE-11503:
---
Summary: MVCC: Handle partition loss policies
Key: IGNITE-11503
URL: https://issues.apache.org/jira/browse/IGNITE-11503
Project: Ignite
Issue Type: Tas
I can propose two improvements here:
1. A simple one. Lets introduce maxConnectionNumber parameter
in ClientConfiguration. As it is easy to implement it may be introduced
together with the new feature to give user an additional control.
2. Asynchronous connection establishment. In this case start
Alexey Platonov created IGNITE-11504:
Summary: [ML] Preprocessor trainers should support new
feature-label extraction API
Key: IGNITE-11504
URL: https://issues.apache.org/jira/browse/IGNITE-11504
Pavel Kuznetsov created IGNITE-11505:
Summary: Validation of starting cache configuration wraps original
exception into Suppressed section
Key: IGNITE-11505
URL: https://issues.apache.org/jira/browse/IGNITE-11
Hi Ignite Developers,
In the separate topic, we've touched the question of next release of Apache
Ignite.
The main reason for the release is Java 11 support, modularity changes
(actually we have a couple of this kind of fixes). Unfortunately, full
modularity support is impossible without 3.0 beca
Can we freeze scope effective immediately, make branch and stabilise whatever
should be finished, producing not emergency but not full regular release?
> On 7 Mar 2019, at 17:21, Dmitriy Pavlov wrote:
>
> Hi Ignite Developers,
>
> In the separate topic, we've touched the question of next rel
Hello!
I think we can surely go with B. It contains fresh Hibernate and Spring
Data support with fixed bugs, which is good while it lasts.
Also there are a lot of Java 11 fixes and cherry-picking them all probably
not much easier than just stabilizing master. We have fixes for other
regressions t
Alexey Kuznetsov created IGNITE-11506:
-
Summary: Web Console: Adjust CSS styles to correctly show "User
name" in top menu.
Key: IGNITE-11506
URL: https://issues.apache.org/jira/browse/IGNITE-11506
Alexander Lapin created IGNITE-11507:
Summary: SQL: Ensure that affinity topology version doesn't change
during PartitionResult construction/application.
Key: IGNITE-11507
URL: https://issues.apache.org/jira/b
Igniters,
How about releasing Ignite 2.8 from the master - creating the release
branch on Monday-Tuesday, as fast as we can? Don't want us to delay with
Java 11 improvements, they are really helpful from the usability standpoint.
After this release, let's introduce a practice of maintenance relea
+1
чт, 7 марта 2019 г., 20:00 Denis Magda :
> Igniters,
>
> How about releasing Ignite 2.8 from the master - creating the release
> branch on Monday-Tuesday, as fast as we can? Don't want us to delay with
> Java 11 improvements, they are really helpful from the usability
> standpoint.
>
> After t
Hello!
Then please fast-forward review and merge
https://issues.apache.org/jira/browse/IGNITE-11299 because it breaks SSL on
Windows under Java 11.
Anything else that needs to be merged before release is branched?
Regards,
--
Ilya Kasnacheev
чт, 7 мар. 2019 г. в 20:07, Nikolay Izhikov :
> +1
Igniters,
Making release from master is not an option. We have a lot of not-yet-ready
and not-yet-tested features. From SQL side this is partition pruning and
SQL views with KILL command.
So if we do not want to release a mess, then there are only two options:
release Java 11 fixes on top of 2.7,
Vova it is not cool I have to remind Ignite veterans about How to
contribute page, it says the master is release ready branch.
Otherwise feature is developed in its own branch.
So my vote goes for master-based release.
чт, 7 мар. 2019 г. в 20:28, Vladimir Ozerov :
> Igniters,
>
> Making release
Vova,
Thanks for the inputs. If it takes weeks to stabilize the master then let's
release from 2.7 cherry-picking Java 11 improvements. We can't wait for
months holding these improvements - the world is switching to Java 11 and
Ignite fails during the first runs presently.
-
Denis
On Thu, Mar 7
Denis, there is not so much difference in Java 9 vs Java 11, so previous
Java 9-efforts done by Igniters should be applicable for 11.
So I don't understand why we can go through the normal release process and
pilot minor releases afterward. Please share a particular case when the
absence of `emerg
Dmitry,
“Master is always releasable” is a myth, let’s do not be naive. We develop
complex product. Many features are being developed in iterations. Many
features are developed by different contributors and have to be aligned
with each other after merge. And in the end all this should be tested an
Dmitriy,
Please find a copy-paste from the first conversation when impactful
usability problems were reported more than a month ago:
*I played with the latest Oracle JDK 11 on Mac OS Mojave. Results are sad:*
- *Starting a node from cmd (ignite.sh) - FAILED*
- *Opening Ignite examples - BA
ARAVINDA REDDY N created IGNITE-11508:
-
Summary: Yarn Ignite deployment: Add support to over ride queue
name through cluster properties
Key: IGNITE-11508
URL: https://issues.apache.org/jira/browse/IGNITE-11508
24 matches
Mail list logo
