Igor Sapego created IGNITE-13116:
Summary: CPP: Can not compile using msvc 15
Key: IGNITE-13116
URL: https://issues.apache.org/jira/browse/IGNITE-13116
Project: Ignite
Issue Type: Bug
So favorite topic =)
> In fact, it's even OK-ish to use it after the ticket name, since we see such
> tickets in our code base. It's just not the default and should not be
> recommended to new users.
Agree here. I would be even more liberal: at least there should be a
consistency among our
Amelchev Nikita created IGNITE-13115:
Summary: Master key name can't be changed if Unicode symbols
present
Key: IGNITE-13115
URL: https://issues.apache.org/jira/browse/IGNITE-13115
Project:
Are you going to provide CVE-2020-1964 patches and patch instructions for
previous Ignite versions?
Regards,
-Nick
From: Sriveena Mattaparthi
Sent: Wednesday, June 3, 2020 9:04 AM
To: u...@ignite.apache.org; dev ; annou...@apache.org;
Apache Security Team
Subject: COMMERCIAL:RE:
+1 for initial dates, RM candidate, need June to finish and test features
Model export/import for ML and a fewminor fixes
ср, 3 июн. 2020 г., 18:05 Sergey Antonov :
> Cluster read-only mode and new cluster state change API.
>
> ср, 3 июн. 2020 г. в 16:10, Ilya Kasnacheev :
>
> > Hello!
> >
> >
Cluster read-only mode and new cluster state change API.
ср, 3 июн. 2020 г. в 16:10, Ilya Kasnacheev :
> Hello!
>
> Can you please clarify what is the scope of 2.9 release?
>
> I have a feeling that we don't really have any big features in the current
> 2.9 code base. No Calcite, etc.
>
> So I'm
Hello.
I will do review of this changes.
> 1 июня 2020 г., в 13:21, Ivan Daschinsky написал(а):
>
> Igor, could you please check my PR?
>
> пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky :
>
>> Thanks you all. Run patch (I've changed some code also) on TC -- all CPP
>> suites are green (GCC,
Chris Dennis created IGNITE-13114:
-
Summary: Off-by-one error in GridPortProcessor port number
assertion
Key: IGNITE-13114
URL: https://issues.apache.org/jira/browse/IGNITE-13114
Project: Ignite
Ivan,
It feels like Val is driving us in the right direction. Is there any reason
for keeping the current logic when servers can open connections to clients?
-
Denis
On Thu, May 21, 2020 at 4:48 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Ivan,
>
> Have you considered
Ilya,
I've assumed that the next 2.10 release will start in August, so folks
can commit their changes without a rush. Another option, everyone can
ask in the current thread to wait for their changes :-)
On Wed, 3 Jun 2020 at 17:29, Ilya Kasnacheev wrote:
>
> Hello!
>
> I think we should have at
Hello!
I think we should have at least a month before code freeze. People may have
code planned for commit and we don't want to rush them and commit
sub-optimal code.
Otherwise, +1.
Regards,
--
Ilya Kasnacheev
ср, 3 июн. 2020 г. в 17:24, Maxim Muzafarov :
> +1 to start release and Alexey
Hello!
Maxim, can you please check this, since you have released 2.8.0.
Regards,
--
Ilya Kasnacheev
вт, 26 мая 2020 г. в 17:59, Alex Panchenko :
> I have the same issue. Can anybody help with this?
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
+1 to start release and Alexey Plekhanov as a release manager.
Alexey, can you clarify why we need a month for scope and code freeze
phases? What should we wait for? Maybe I'm missing something, but the
scope for the release already exists.
So, I'd like to suggest the following dates:
Code
Denis Garus created IGNITE-13113:
Summary: CacheEvent#subjectId for cache events with types
EventType#EVTS_CACHE
Key: IGNITE-13113
URL: https://issues.apache.org/jira/browse/IGNITE-13113
Project:
Thanks, Could you please confirm when the analysis will be updated here for the
CVE logged.
https://nvd.nist.gov/vuln/detail/CVE-2020-1963
Regards,
Sriveena
From: Юрий
Sent: 03 June 2020 16:02
To: dev ; u...@ignite.apache.org; annou...@apache.org;
Apache Security Team ; Sriveena Mattaparthi
Pavel,
Form my point of view, your example doesn't break the format rule.
Moreover, the historical aspect also encourages us to follow this
format in the future (again because it makes easier parsing of
commits' messages).
On Wed, Jun 3, 2020 at 4:44 PM Pavel Tupitsyn wrote:
>
> Andrey, Ilya,
>
Hello!
I think that it's OK to use colon anywhere in a commit message, other than
directly after the ticket name.
In fact, it's even OK-ish to use it after the ticket name, since we see
such tickets in our code base. It's just not the default and should not be
recommended to new users.
Regards,
Denis Garus created IGNITE-13112:
Summary: CacheEvent#subjectId is always null for cache events with
types EVT_CACHE_STARTED and EVT_CACHE_STOPPED
Key: IGNITE-13112
URL:
Andrey, Ilya,
I agree that we should follow a standard.
What would you say about .NET tickets/PRs?
Since the very beginning all those tickets are called ".NET: Foo Bar",
and commit messages are "IGNITE- .NET: Add Foo Bar".
Is it ok to continue like this, or do you think we should remove ":"
I've prepared PR [1]
I already tried to discuss commit message format [2] but stumbled upon
some criticism. I still believe that we have to follow only one
standard. It is unrelated with any annoying. It is just normal
practice which also allows avoid of precedents with references to any
+1 To start release process for 2.9
+1 For Alexey Plekhanov as a release manager.
> 3 июня 2020 г., в 16:34, Alex Plehanov написал(а):
>
> Ilya,
>
> We already have a lot of features implemented in the master branch, but not
> released (perhaps not so big as Calcite, but still useful), some of
Ilya,
We already have a lot of features implemented in the master branch, but not
released (perhaps not so big as Calcite, but still useful), some of them
already mentioned in the previous thread:
- Sandbox for user-defined code
- .NET: Native Near Cache
- TDE - Phase-2. Master key rotation
-
Cellular switch
On Wed, Jun 3, 2020 at 4:10 PM Nikolay Izhikov wrote:
> Snapshots.
>
> > 3 июня 2020 г., в 16:10, Ilya Kasnacheev
> написал(а):
> >
> > Hello!
> >
> > Can you please clarify what is the scope of 2.9 release?
> >
> > I have a feeling that we don't really have any big features in
Hello!
I have just noticed the following:
The pull request title is treated as the final commit message.
The following pattern must be used: IGNITE-12407: Add Cluster API support
to Java thin client
However, this format conflicts with our "how to contribute" guide:
- Rename review to include
Hello!
Can you please clarify what is the scope of 2.9 release?
I have a feeling that we don't really have any big features in the current
2.9 code base. No Calcite, etc.
So I'm asking whether it is worth it.
Regards,
--
Ilya Kasnacheev
ср, 3 июн. 2020 г. в 14:45, Alex Plehanov :
> Hello
Snapshots.
> 3 июня 2020 г., в 16:10, Ilya Kasnacheev
> написал(а):
>
> Hello!
>
> Can you please clarify what is the scope of 2.9 release?
>
> I have a feeling that we don't really have any big features in the current
> 2.9 code base. No Calcite, etc.
>
> So I'm asking whether it is worth
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
Vladimir Steshin created IGNITE-13111:
-
Summary: Simplify backward checking of node connection.
Key: IGNITE-13111
URL: https://issues.apache.org/jira/browse/IGNITE-13111
Project: Ignite
++1 for Alexey as a release manager, that's good we are keeping a rotation
of RMs so every committer/PMC knows how to release the code.
0 for dates, actually, it is up to contributors to propose alternatives.
All in all, it is up to the discussion's course.
Sincerely,
Dmitriy Pavlov
ср, 3 июн.
Hello Igniters,
AI 2.8.1 is finally released and as we discussed here [1] its time to start
the discussion about 2.9 release.
I want to propose myself to be the release manager of the 2.9 release.
What about release time, I agree with Maxim that we should deliver features
as frequently as
Hello!
I think it makes sense.
I think we should not over-engineer it now. Let's just allow to specify
your own CacheConfiguration and take all the risks.
Regards,
--
Ilya Kasnacheev
вт, 2 июн. 2020 г. в 17:37, Vladimir Pligin :
> Hi Igniters!
>
> It seems that AtomicConfiguration
> (
>
Hi All,
Apache Ignite 2.8.1 has been released. The release contain fix of critical
vulnerability
CVE-2020-1963: Apache Ignite access to file system through predefined H2
SQL functions
Severity: Critical
Vendor:
The Apache Software Foundation
Versions Affected:
All versions of Apache Ignite up
Guys,
I've taken the liberty of creating the ticket
(https://issues.apache.org/jira/browse/IGNITE-13110) for the proposed
changes.
I did some prototyping as well. You may find the draft code/test
changes in PR https://github.com/apache/ignite/pull/7893
Would appreciate if you can look at it and
Sergey Kalashnikov created IGNITE-13110:
---
Summary: An option to validate field types against SQL schema on
key-value insert
Key: IGNITE-13110
URL: https://issues.apache.org/jira/browse/IGNITE-13110
Amelchev Nikita created IGNITE-13109:
Summary: Skip metastorage entries that can not be unmarshalled
Key: IGNITE-13109
URL: https://issues.apache.org/jira/browse/IGNITE-13109
Project: Ignite
Maxim Muzafarov created IGNITE-13108:
Summary: Decrease number of clients for IgniteCache150ClientsTest
Key: IGNITE-13108
URL: https://issues.apache.org/jira/browse/IGNITE-13108
Project: Ignite
36 matches
Mail list logo
