Maksim Timonin created IGNITE-14206:
---
Summary: 2.8.1 inlines POJO but ignores it since 2.9.0
Key: IGNITE-14206
URL: https://issues.apache.org/jira/browse/IGNITE-14206
Project: Ignite
Issue
Hi,
Please grant me JIRA permissions. My user id is atri
--
Regards,
Atri
Apache Concerted
Hello!
There was a ticket filed about the new feature, transactions in C++ thin
client, making this feature unusable if there's more than one connection
endpoint:
https://issues.apache.org/jira/browse/IGNITE-14204
I don't think this is a genuine blocker for 2.10, since there is a
workaround (use
Hello!
I have already granted permissions to this account, now you should be able
to assign issues to yourself.
Mind the
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
Regards,
--
Ilya Kasnacheev
чт, 18 февр. 2021 г. в 13:12, Atri Sharma :
> Hi,
>
> Please grant me JIRA
Hi, Nikolay!
Have we reached a consensus?
16.02.2021, 17:09, "ткаленко кирилл" :
> Hi, Zhenya!
>
> Users can also use it, I see nothing wrong with the presence of two metrics.
>
> 16.02.2021, 16:50, "Zhenya Stanilovsky" :
>> Kirill, is it good practice to have a metrics for internal use? Don`t t
Hello, Kirill.
Can you, please, write down your proposal?
What metrics you want to add in the Ignite?
> 18 февр. 2021 г., в 14:11, ткаленко кирилл написал(а):
>
> Hi, Nikolay!
>
> Have we reached a consensus?
>
> 16.02.2021, 17:09, "ткаленко кирилл" :
>> Hi, Zhenya!
>>
>> Users can also use
Hello, Nikolay!
org.apache.ignite.mxbean.DataStorageMetricsMXBean#getLastArchivedSegmentIndex -
Get the index of the last archived segment.
org.apache.ignite.mxbean.DataStorageMetricsMXBean#getMaxSizeCompressedArchivedSegment
- Getting the size of the maximum compressed segment in the archive.
Andrey Kuznetsov created IGNITE-14207:
-
Summary: Access to system views is not controlled by security
processor
Key: IGNITE-14207
URL: https://issues.apache.org/jira/browse/IGNITE-14207
Project: I
Folks,
Do we have any estimations of how long does it take to fix the issue
[1] in C++ thin client? The bug must be fixed for sure, however, I
tend to continue with the release (if fixing the bug require a few
weeks) and prepare a batch of fixes for the 2.10.1.
[1] https://issues.apache.org/jir
Hi! I've today found an issue [1], there is wrong handling of inlined POJO.
This bug appeared in 2.9.0 and makes it impossible to work with
multi-column indexes created on old AI versions that contain inlined POJO
keys in the middle.
I'm working on the fix and asked Konstantin Orlov to review it.
Maxim,
I believe I could fix the ticket [1] by the end of the next week.
[1] https://issues.apache.org/jira/browse/IGNITE-14204
Best Regards,
Igor
On Thu, Feb 18, 2021 at 6:30 PM Max Timonin wrote:
> Hi! I've today found an issue [1], there is wrong handling of inlined POJO.
> This bug appea
Pavel Tupitsyn created IGNITE-14208:
---
Summary: .NET: Examples multi targeting
Key: IGNITE-14208
URL: https://issues.apache.org/jira/browse/IGNITE-14208
Project: Ignite
Issue Type: Improveme
Vyacheslav Koptilin created IGNITE-14209:
Summary: Need to implement data rebalancing which is required by
atomic/transactional caches
Key: IGNITE-14209
URL: https://issues.apache.org/jira/browse/IGNITE-1
Maxim, Igor,
Thanks for sharing details.
Let's wait for these fixes.
[1] https://issues.apache.org/jira/browse/IGNITE-14206
[2] https://issues.apache.org/jira/browse/IGNITE-14204
On Thu, 18 Feb 2021 at 18:35, Igor Sapego wrote:
>
> Maxim,
>
> I believe I could fix the ticket [1] by the end of t
Surkov Aleksandr created IGNITE-14210:
-
Summary: Tracing: add tracing for thin client
Key: IGNITE-14210
URL: https://issues.apache.org/jira/browse/IGNITE-14210
Project: Ignite
Issue Type:
Big +1 for this.
On a related note, we just ran into a versioning issue related to the .Net
Standard 2.0 support in IA. We use .Net Core 3.1 with IA 2.8.1 and wanted
to use the StackExchange Redis client. However, the latest client has a
dependency on System.Diagnostics.PerformanceCounter 5.0.0, b
Was there a resolution for this issue?
On Mon, Sep 7, 2020 at 9:40 AM Ilya Kasnacheev
wrote:
> Hello!
>
> I wonder why there's no stack traces for all the threads.
>
> I wonder if somebody from the development side will step in (2.8.1):
>
> [05:57:16,193][SEVERE][sys-stripe-15-#16][] Critical sy
Igor Sapego created IGNITE-14211:
Summary: Python thin: SQL API is broken
Key: IGNITE-14211
URL: https://issues.apache.org/jira/browse/IGNITE-14211
Project: Ignite
Issue Type: Bug
Affects
18 matches
Mail list logo