Maxim Muzafarov created IGNITE-14069:
Summary: Add RELEASE_NOTES for 2.10
Key: IGNITE-14069
URL: https://issues.apache.org/jira/browse/IGNITE-14069
Project: Ignite
Issue Type: Task
Nikita, Folks,
All documentation tasks from the *[list #2]* [1] that you mentioned
above have been processed and merged to the release branch.
[1]
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Apache-Ignite-Release-2-10-time-scope-manager-tp50037p51061.html
On Mon, 25 Jan
Vladimir Steshin created IGNITE-14068:
-
Summary: Infinite node persistance in the ring while outcoming
connections are lost
Key: IGNITE-14068
URL: https://issues.apache.org/jira/browse/IGNITE-14068
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
Stephen Darlington created IGNITE-14067:
---
Summary: CREATE TABLE with template doesn't use
isEncryptionEnabled flag
Key: IGNITE-14067
URL: https://issues.apache.org/jira/browse/IGNITE-14067
Hi!
No, we basically have a problem with the growth of WAL archive.
26.01.2021, 19:06, "Vishwas Bm" :
> Hi,
>
> Is this related to issue seen with
> IGNITE-13912 ?
>
> I had hit IGNITE-13912 when I was using ignite 2.9 release.
> I am yet to try my use case with the fix provided as part of
As for me, correct approach is to trigger checkpoint when we are too close
to WAL archive size limit.
The main purpose of these mechanism is to provide durability, so we
should think about not to fail node, nor to delete data voluntary,
but prevent possible data loss.
вт, 26 янв. 2021 г. в 19:13,
Hello !
this is unclear for me, all you described near brings no info why node work
improperly and why FH can possibly fail this node. Can you explain ?
>Hello, everyone!
>
>Currently, property DataStorageConfiguration#maxWalArchiveSize is not working
>as expected by users. We can easily go
Hi,
Is this related to issue seen with
IGNITE-13912 ?
I had hit IGNITE-13912 when I was using ignite 2.9 release.
I am yet to try my use case with the fix provided as part of IGNITE-13912
Regards,
Vishwas
On Tue, 26 Jan, 2021, 21:18 ткаленко кирилл, wrote:
> Hello, everyone!
>
> Currently,
Lukas Eder created IGNITE-14066:
---
Summary: JDBC DatabaseMetaData::getColumns reports REAL column
type as FLOAT
Key: IGNITE-14066
URL: https://issues.apache.org/jira/browse/IGNITE-14066
Project: Ignite
Hello, everyone!
Currently, property DataStorageConfiguration#maxWalArchiveSize is not working
as expected by users. We can easily go beyond this limit and overflow the disk,
which will lead to errors and a crash of the node. I propose to fix this
behavior and not let WAL archive overflow.
It
Lukas Eder created IGNITE-14065:
---
Summary: JDBC DatabaseMetaData::getColumns should return vendor
specific data types, like UUID, in TYPE_NAME
Key: IGNITE-14065
URL:
Hello, Alexey.
Sorry, for the long answer.
> - The interface exposes WALRecord which is a private API
Not it's fixed.
CDC consumer should use public API to get notifications about a data change.
This API can be found in IEP [1] and PR [2]
```
@IgniteExperimental
public interface
Pavel Tupitsyn created IGNITE-14064:
---
Summary: .NET: Incorrect table name when query type is generic
Key: IGNITE-14064
URL: https://issues.apache.org/jira/browse/IGNITE-14064
Project: Ignite
Sergey Kadaner created IGNITE-14063:
---
Summary: Error: Failed to get java major version (unknown
'java.version' format) [ver=14-ea]
Key: IGNITE-14063
URL: https://issues.apache.org/jira/browse/IGNITE-14063
Ivan Bessonov created IGNITE-14062:
--
Summary: Create basic classes and interfaces for traversable
configuration tree.
Key: IGNITE-14062
URL: https://issues.apache.org/jira/browse/IGNITE-14062
Peter Ivanov created IGNITE-14061:
-
Summary: extdata modules are incorrectly published
Key: IGNITE-14061
URL: https://issues.apache.org/jira/browse/IGNITE-14061
Project: Ignite
Issue Type:
17 matches
Mail list logo
