Andrey Aleksandrov created IGNITE-11724:
---
Summary: IgniteSpark integration forget to close the IgniteContext
and stops the client node in case if error during PairFunction logic
Key: IGNITE-11724
URL:
Andrey Aleksandrov created IGNITE-11723:
---
Summary: IgniteSpark integration should support skipStore option
for internal dataStreamer (IgniteRdd and Ignite DataFrame)
Key: IGNITE-11723
URL:
Semen Boikov created IGNITE-11722:
-
Summary: Batch BPlustTree updates for cache batch operations
Key: IGNITE-11722
URL: https://issues.apache.org/jira/browse/IGNITE-11722
Project: Ignite
Anton Kurbanov created IGNITE-11721:
---
Summary: IgniteJdbcDriver with streaming enabled doesn't use
IgniteDataStreamer on executeBatch
Key: IGNITE-11721
URL: https://issues.apache.org/jira/browse/IGNITE-11721
Hello, Ignite.
Finally, I've implemented this ticket! :)
Jira - https://issues.apache.org/jira/browse/IGNITE-9113
PR - https://github.com/apache/ignite/pull/6388
Tests seems to be OK.
Anyone wants to take a look?
В Чт, 09/08/2018 в 16:41 +0300, Alexey Goncharuk пишет:
> Once the OS gave us the
Taras Ledkov created IGNITE-11720:
-
Summary: Document new SQL system view "COLUMNS"
Key: IGNITE-11720
URL: https://issues.apache.org/jira/browse/IGNITE-11720
Project: Ignite
Issue Type: Task
Sergey Antonov created IGNITE-11719:
---
Summary: Document cluster read-only mode
Key: IGNITE-11719
URL: https://issues.apache.org/jira/browse/IGNITE-11719
Project: Ignite
Issue Type: New
Denis Garus created IGNITE-11718:
Summary: Authorizing of SERVICE_INVOKE permission
Key: IGNITE-11718
URL: https://issues.apache.org/jira/browse/IGNITE-11718
Project: Ignite
Issue Type:
Hi. Fix Version is time-to-time set before reviewing a patch, but for open
tickets fix version does not mean too much.
Open tickets migrated from version being released to the next one
automatically. Currently, all fixed issues go to 2.8 by default, and some
of them were assigned to 2.7.5 (scope
Ilya Borisov created IGNITE-11717:
-
Summary: Web console: project generation runtime error caused by
IGFS
Key: IGNITE-11717
URL: https://issues.apache.org/jira/browse/IGNITE-11717
Project: Ignite
Ilya Borisov created IGNITE-11716:
-
Summary: Web console: can't select cluster memory eviction mode
Key: IGNITE-11716
URL: https://issues.apache.org/jira/browse/IGNITE-11716
Project: Ignite
Kresimir Horvat created IGNITE-11715:
Summary: Add support for nojmx flag when running Ignite in docker
Key: IGNITE-11715
URL: https://issues.apache.org/jira/browse/IGNITE-11715
Project: Ignite
Nope, I meant whether fixVersion was set before or as part of or after patch
review. From your answer I understand that correct answer is: after patch
review.
-
Oleksii
-Original Message-
From: Ilya Kasnacheev
Sent: Wednesday, April 10, 2019 12:00 PM
To: dev@ignite.apache.org
Ilya Borisov created IGNITE-11714:
-
Summary: Web console: multiple select items overflow
Key: IGNITE-11714
URL: https://issues.apache.org/jira/browse/IGNITE-11714
Project: Ignite
Issue Type:
Hello!
Usually you set fixVersion when your ticket is committed to master and it
becomes obvious.
It's not like you can force community to do a ticket by setting urgent
fixVersion, if that's what you are asking.
Regards,
--
Ilya Kasnacheev
ср, 10 апр. 2019 г. в 11:34, Oleksii Mohylin :
>
Ilya Borisov created IGNITE-11713:
-
Summary: Web console: cluster configuration events content fit
issue
Key: IGNITE-11713
URL: https://issues.apache.org/jira/browse/IGNITE-11713
Project: Ignite
Thank you! Just a follow-up question, who and when can decide on fixVersion of
a ticket? Is that something contributors can do, or reviewers or someone else?
I couldn't find this in wiki.
-
Oleksii
-Original Message-
From: Denis Magda
Sent: Wednesday, April 10, 2019 2:58 AM
To: dev
Roman Kondakov created IGNITE-11712:
---
Summary: SQL: review security check for SQL/DML queries
Key: IGNITE-11712
URL: https://issues.apache.org/jira/browse/IGNITE-11712
Project: Ignite
18 matches
Mail list logo
