Alexey Kuznetsov created IGNITE-10875:
-
Summary: Web Console: Update tooltip
Key: IGNITE-10875
URL: https://issues.apache.org/jira/browse/IGNITE-10875
Project: Ignite
Issue Type:
Pavel Voronkin created IGNITE-10876:
---
Summary: finishExchangeOnCoordinator parallelization
Key: IGNITE-10876
URL: https://issues.apache.org/jira/browse/IGNITE-10876
Project: Ignite
Issue
Pavel Voronkin created IGNITE-10877:
---
Summary: GridAffinityAssignment.initPrimaryBackupMaps memory
pressure
Key: IGNITE-10877
URL: https://issues.apache.org/jira/browse/IGNITE-10877
Project: Ignite
Added dev@ignite.apache.org.
Should I log Jira for this issue?
Thanks,
Akash
On Tue, Jan 8, 2019 at 6:16 PM Akash Shinde wrote:
> Hi,
>
> No both nodes, client and server are running on Ignite 2.7 version. I am
> starting both server and client from Intellij IDE.
>
> Version printed in
Aleksey Zinoviev created IGNITE-10870:
-
Summary: [ML] Add an example for KNN/LogReg and multi-class task
full Iris dataset
Key: IGNITE-10870
URL: https://issues.apache.org/jira/browse/IGNITE-10870
Andrew Mashenkov created IGNITE-10871:
-
Summary: MVCC: Fix SPI exception handling in mvcc mode.
Key: IGNITE-10871
URL: https://issues.apache.org/jira/browse/IGNITE-10871
Project: Ignite
Aleksey Zinoviev created IGNITE-10866:
-
Summary: [ML] Add an example of LogRegression model loading
Key: IGNITE-10866
URL: https://issues.apache.org/jira/browse/IGNITE-10866
Project: Ignite
Hi,
I have question related to subject. How do you think should we track
EXPLAIN queries also? I see reasons as to skip it and as include to history:
pros:
We will have full picture and see all queries.
cons:
Such queries can be considered as investigate/debug/service queries and can
push out
Aleksey Zinoviev created IGNITE-10869:
-
Summary: [ML] Add MultiClass classification metrics
Key: IGNITE-10869
URL: https://issues.apache.org/jira/browse/IGNITE-10869
Project: Ignite
Ilya Kasnacheev created IGNITE-10867:
Summary: Document work-around JDK upgrade against command-line
parsing bug on Windows
Key: IGNITE-10867
URL: https://issues.apache.org/jira/browse/IGNITE-10867
Hello!
I have resolved the ticket, linked JDK bug. Please update docs.
I have created a Docs issue
https://issues.apache.org/jira/browse/IGNITE-10867
Regards,
--
Ilya Kasnacheev
пн, 31 дек. 2018 г. в 20:45, Denis Magda :
> Ivan, thanks!
>
> Ilya, could you confirm that is your issue and
Artem Budnikov created IGNITE-10868:
---
Summary: WAL segments are removed from WAL archive after each
checkpoint
Key: IGNITE-10868
URL: https://issues.apache.org/jira/browse/IGNITE-10868
Project:
Hi Igniters,
Please find a free minute and fill survey:
https://s.apache.org/oxTr DEADLINE: 15 February 2019
Sincerely,
Dmitriy Pavlov
-- Forwarded message -
From: Sally Khudairi
Date: ср, 9 янв. 2019 г. в 09:13
Subject: Fwd: The ASF needs your help! "The Apache Way To
Taras Ledkov created IGNITE-10864:
-
Summary: JDK11: fix check jdk version at the ignite.bat
Key: IGNITE-10864
URL: https://issues.apache.org/jira/browse/IGNITE-10864
Project: Ignite
Issue
Aleksey Zinoviev created IGNITE-10865:
-
Summary: [ML] [Umbrella] Integration with Spark ML
Key: IGNITE-10865
URL: https://issues.apache.org/jira/browse/IGNITE-10865
Project: Ignite
Issue
Hi Dmitry,
Looks like repository has been transferred to GitBox,
but for now we still have incorrect links on wiki and ignite web site.
I've created a ticket [1]. Can someone fix this?
https://issues.apache.org/jira/browse/IGNITE-10863
On Sun, Dec 30, 2018 at 1:28 AM Dmitriy Pavlov wrote:
>
Done for the wiki, we need update site.
ср, 9 янв. 2019 г. в 12:28, Andrey Mashenkov :
> Hi Dmitry,
>
> Looks like repository has been transferred to GitBox,
> but for now we still have incorrect links on wiki and ignite web site.
>
> I've created a ticket [1]. Can someone fix this?
>
>
In the TC Bot, I used to create the second cache with CacheV2 name and
migrate needed data from Cache V1 to V2.
After CacheV1 destroy(), files are removed and disk space is freed.
ср, 9 янв. 2019 г. в 12:04, Павлухин Иван :
> Vyacheslav,
>
> Have you investigated how other vendors (Oracle,
Seems, the next step is to integrate tcbot with github.
It will be nice to have an opportunity to ask the bot to check PR right
from PR.
On Wed, Jan 9, 2019 at 12:04 PM Anton Vinogradov wrote:
> >> Committers can set up account matching between GitHub and Apache. After
> >> this setup, you can
Hello!
Do you have a reproducer project to reliably confirm this issue?
Regards,
--
Ilya Kasnacheev
ср, 9 янв. 2019 г. в 12:39, Akash Shinde :
> Added dev@ignite.apache.org.
>
> Should I log Jira for this issue?
>
> Thanks,
> Akash
>
>
>
> On Tue, Jan 8, 2019 at 6:16 PM Akash Shinde wrote:
Oscar, great use-case, and ML-related developers (me too) will happy to
help you with this case.
Could you please answer a three questions?
1) What kind of types (Java types or SQL types) could be in column
properties?
2) Have all data series (observation) has the same schema with equal number
Andrew Mashenkov created IGNITE-10863:
-
Summary: Fix incorrect links to git repositories.
Key: IGNITE-10863
URL: https://issues.apache.org/jira/browse/IGNITE-10863
Project: Ignite
Issue
Vyacheslav,
Have you investigated how other vendors (Oracle, Postgres) tackle this problem?
I have one wild idea. Could the problem be solved by stopping a node
which need to be defragmented, clearing persistence files and
restarting the node? After rebalance the node will receive all data
back
>> Committers can set up account matching between GitHub and Apache. After
>> this setup, you can merge pull requests from GitHub Web UI
That's awesome!
On Mon, Dec 31, 2018 at 1:49 AM Dmitriy Pavlov wrote:
> Dear Ignite Developers,
>
> I would like to repeat announce from other thread with
Hi,
Anton, can you review ticket for examples [1]?
[1] https://issues.apache.org/jira/browse/IGNITE-6826
пн, 24 дек. 2018 г., 15:23 Anton Vinogradov a...@apache.org:
> Folks,
>
> The important thing here is that 99% of "final static" ip-finders were
> removed. (~800 pcs.)
> Non-static, mostly,
Yuriy,
I think, for the sake of code simplicity we can track all queries.
in other case we will need to parse SQL text and detect that current query
is the EXPLAIN one.
--
Alexey Kuznetsov
Gabriel Jimenez created IGNITE-10872:
Summary: Queue Draining on Graceful Shutdowns
Key: IGNITE-10872
URL: https://issues.apache.org/jira/browse/IGNITE-10872
Project: Ignite
Issue Type:
Pavel Vinokurov created IGNITE-10873:
Summary: CorruptedTreeException during simultaneous cache put
operations
Key: IGNITE-10873
URL: https://issues.apache.org/jira/browse/IGNITE-10873
Project:
Hi,
MVCC caches have the same ordering guarantees as non-MVCC caches, i.e. two
subsequent updates on a single key will be delivered in proper order. There
is no guarantees Order of updates on two subsequent transactions affecting
the same partition may be guaranteed with current implementation
Alexey Kukushkin created IGNITE-10874:
-
Summary: JDBC thin driver metadata misses caches with
queryEntities and names containing underscores
Key: IGNITE-10874
URL:
30 matches
Mail list logo