Stanislav Lukyanov created IGNITE-10952:
---
Summary: Document SET STREAMING command options
Key: IGNITE-10952
URL: https://issues.apache.org/jira/browse/IGNITE-10952
Project: Ignite
Issue
Ilya Kasnacheev created IGNITE-10953:
Summary: Cassandra examples should not use test classes
Key: IGNITE-10953
URL: https://issues.apache.org/jira/browse/IGNITE-10953
Project: Ignite
Iss
The wiki's article [1] has been updated according to the merged solution [2].
[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95654584
[2] https://issues.apache.org/jira/browse/IGNITE-9607
On Fri, Dec 28, 2018 at 1:10 PM Vyacheslav Daradur wrote:
>
> Igniters,
>
> to have an
Pavel,
Yeah, it makes sense, but to me it seems that this approach can lead
to more complicated client logic, as it will require to make additional call
to every server, that reports affinity topology change.
Guys, WDYT?
Best Regards,
Igor
On Tue, Jan 15, 2019 at 10:59 PM Pavel Tupitsyn
wrote
Welcome to the community!
Feel free to mention me in mails and tickets related to C++ to draw
my attention, if you need any advice.
Best Regards,
Igor
On Tue, Jan 15, 2019 at 9:42 PM Denis Magda wrote:
> Hello,
>
> Welcome to the community! Added you to the contributors' list in JIRA. Feel
>
Hi, Prehistoricpenguin!
It would be great if you will be able to finish a solution [1]. But
I'm not sure that it's a good ticket to start contributing because of
interplatform complexity. Anyway, feel free to contact me in case of
working on the task.
[1] https://issues.apache.org/jira/browse/IGN
Andrew Mashenkov created IGNITE-10954:
-
Summary: MVCC: Umute fixed tests.
Key: IGNITE-10954
URL: https://issues.apache.org/jira/browse/IGNITE-10954
Project: Ignite
Issue Type: Test
Artem Malykh created IGNITE-10955:
-
Summary: [ML] Migrate boosting implementation to sequential
trainers composition combinator
Key: IGNITE-10955
URL: https://issues.apache.org/jira/browse/IGNITE-10955
Igor Seliverstov created IGNITE-10956:
-
Summary: MVCC TX: Move queryEnlisted flag from
IgniteTxLocalAdapter to IgniteTxState
Key: IGNITE-10956
URL: https://issues.apache.org/jira/browse/IGNITE-10956
Alexei Scherbakov created IGNITE-10957:
--
Summary: Reduce EnsuredMessageHistory heap occupation
Key: IGNITE-10957
URL: https://issues.apache.org/jira/browse/IGNITE-10957
Project: Ignite
I
Yury,
How do we differentiate between logical and physical reads?
Also, it looks counter-intuitive when "CACHE" is used in the name of the
views for SQL table related statistics. It's still hard to explain the user
the relations between caches and tables. Hopefully, this will be fixed in
3.0 with
Yury,
I do support the latter concatenation approach. It's simple and correlates
with what other DBs do. Plus, it can be passed to KILL command without
complications. Thanks for thinking this through!
As for the killing of all queries on a particular node, not sure that's a
relevant use case. I w
Hi,
According to plan described in corresponding ticket [1] we are going
to extend TransactionConfiguration with parameters related to deadlock
detection. As you might remember suggested deadlock detection approach
is going to be enabled for MVCC caches only. Let's discuss what
properties should b
Denis,
Physical reads is load page from storage to memory.
Logical reads is read page which already in memory.
We gather IO statistics on CACHE_GROUP level due to Ignite use one page to
keep all caches related to one cache group. Unfortunately gathering on
table level will be expensive due to th
Ivan Fedotov created IGNITE-10958:
-
Summary: Migrate from Junit 4 to 5
Key: IGNITE-10958
URL: https://issues.apache.org/jira/browse/IGNITE-10958
Project: Ignite
Issue Type: Task
R
Wouldn't disk_read and memory_read be better naming?
-
Denis
On Wed, Jan 16, 2019 at 7:38 AM Юрий wrote:
> Denis,
>
> Physical reads is load page from storage to memory.
> Logical reads is read page which already in memory.
>
> We gather IO statistics on CACHE_GROUP level due to Ignite use one
Denis Mekhanikov created IGNITE-10959:
-
Summary: Memory leaks in continuous query handlers
Key: IGNITE-10959
URL: https://issues.apache.org/jira/browse/IGNITE-10959
Project: Ignite
Issue
Mikhail Cherkasov created IGNITE-10960:
--
Summary: Thin client cannot retrieve data that was inserted with
the Thick Ignite client when using a composite key
Key: IGNITE-10960
URL: https://issues.apache.org/ji
> to every server
I did not think of this issue. Now I agree with your approach.
Can you please add an explanation of this to the IEP?
Thanks!
On Wed, Jan 16, 2019 at 2:53 PM Igor Sapego wrote:
> Pavel,
>
> Yeah, it makes sense, but to me it seems that this approach can lead
> to more complica
Dmitriy,
Thanks. I will update ML documentation when it is available for my.
ticket: https://issues.apache.org/jira/browse/IGNITE-8532
Thanks.
Turik
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Ilya Borisov created IGNITE-10961:
-
Summary: Web console: add more countries
Key: IGNITE-10961
URL: https://issues.apache.org/jira/browse/IGNITE-10961
Project: Ignite
Issue Type: Improvement
Igniters,
After putting some data with a user-defined key with a thick client, it's
impossible to retrieve it with a thin
client.https://issues.apache.org/jira/browse/IGNITE-10960(I was not sure it was
a bug, so I first reported the issue to the user ml, Mikhail thanks for
checking and the jira
22 matches
Mail list logo
