Andrey,
Some rules are good, some rules are bad :)
If you create such a script so that it relies on having a colon in every
message, it will never work, simply because people make mistakes. The only
consequence of such a rule would be that we will have to fight it forever
trying to enforce it.
Ivan, Val,
> But is it really important whether someone puts a colon, a dash, or just a
> space after the ticket number?
Absolutely not important. But every time when you want to write script
for processing commit messages in some way you should check what
exactly format committers use.
I do
Hi Igniters,
I thought that some of you could benefit from joining a webinar about
in-memory computing essentials [1] on March 25th, where Ignite is used as a
reference platform for explanation/demonstration of the main topics. Some
of you might have watched the original version, that had bee
Igor Seliverstov created IGNITE-12820:
-
Summary: Calcite integration. Do not use AbstarctConverter while
planning.
Key: IGNITE-12820
URL: https://issues.apache.org/jira/browse/IGNITE-12820
Igor Seliverstov created IGNITE-12819:
-
Summary: Calcite integration. Cost system.
Key: IGNITE-12819
URL: https://issues.apache.org/jira/browse/IGNITE-12819
Project: Ignite
Issue Type:
Hi, Ignite Users and Enthusiasts!
Please take a few minutes to go through the small survey[1] about Ignite
2.8. The survey has only three questions and is anonymous. Your answers
will help contributors to understand which changes were most interesting
and relevant to users.
Please answer before
Hi Maxim,
Those JIRA labels support the current process that assumes the creation of
a documentation ticket before a development ticket is closed. If a
contributor believes there is no need to update the docs (like in the case
of bug fixes) then "Documentation required" will stay disabled.
Vladislav Pyatkov created IGNITE-12818:
--
Summary: SoLinger is not set for reader-sockets in discovery
Key: IGNITE-12818
URL: https://issues.apache.org/jira/browse/IGNITE-12818
Project: Ignite
Denis,
>From my recent practice with the release check-boxes "Release notes
required" and "Documentation required" also was not so helpful as
expected. Can we remove them from JIRA issues?
There is no magic pill to not forget to document improvements, but I
think a wide discussion of each major
Anton Kalashnikov created IGNITE-12817:
--
Summary: Streamer threads don't update timestamp
Key: IGNITE-12817
URL: https://issues.apache.org/jira/browse/IGNITE-12817
Project: Ignite
Issue
Igniters,
I support Nikolay Izhikov as the release manager of 2.8.1 Apache
Ignite release. Since no one else of committers, PMCs expressed a
desire to lead this release I think we can close this question and
focus on the release scope and dates.
Ivan,
You helped me configuring TC.Bot that
Hi,
I propose to add the issue [1] related to SQL query execution to this scope.
We had omitted this case and Ignite 2.8 contains serious SQL issue:
cursor of a local query is not thread-safe.
It is root cause of several SQL issue, e.g. JDBC thin client cannot
execute query from replicated
Surkov Aleksandr created IGNITE-12816:
-
Summary: Create a table for the existing cache
Key: IGNITE-12816
URL: https://issues.apache.org/jira/browse/IGNITE-12816
Project: Ignite
Issue
Hello Igniters!
I corrected all the comments. If there are no more comments, please accept the
PR.
Ticket: https://issues.apache.org/jira/browse/IGNITE-8152
PR: https://github.com/apache/ignite/pull/7521
Thanks in advance!
Nikolay Izhikov created IGNITE-12815:
Summary: [IEP-39] Management API to cancel SQL queries.
Key: IGNITE-12815
URL: https://issues.apache.org/jira/browse/IGNITE-12815
Project: Ignite
Nikolay Izhikov created IGNITE-12814:
Summary: [IEP-39] Management API to cancel continuous queries.
Key: IGNITE-12814
URL: https://issues.apache.org/jira/browse/IGNITE-12814
Project: Ignite
Nikolay Izhikov created IGNITE-12813:
Summary: [IEP-39] Management API to cancel scan queries.
Key: IGNITE-12813
URL: https://issues.apache.org/jira/browse/IGNITE-12813
Project: Ignite
Nikolay Izhikov created IGNITE-12812:
Summary: [IEP-39] Management API to cancel transaction.
Key: IGNITE-12812
URL: https://issues.apache.org/jira/browse/IGNITE-12812
Project: Ignite
Nikolay Izhikov created IGNITE-12811:
Summary: [IEP-39] Management API to cancel services.
Key: IGNITE-12811
URL: https://issues.apache.org/jira/browse/IGNITE-12811
Project: Ignite
Issue
Nikolay Izhikov created IGNITE-12810:
Summary: [IEP-39] Management API to cancel compute tasks.
Key: IGNITE-12810
URL: https://issues.apache.org/jira/browse/IGNITE-12810
Project: Ignite
Hi Alexei, Denis,
One of the main usecases of thin client authentication is to be able to audit
the changes done using the thin client user.
To enable that :
We really need to resolve this concern as well :
https://issues.apache.org/jira/browse/IGNITE-12781
( Incorrect security subject id is
My top priorities:
- Thin Client API extension: Compute, Continuous Queries, Services
- .NET Near Cache: soon to come in Thick API, to be investigated for
Thin Clients
- .NET Modernization for Ignite 3.0: drop legacy .NET Framework support,
target .NET Standard 2.0, add nullable
22 matches
Mail list logo
