GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/5468
IGNITE-10374 if rebalance isn't restarted no need to disable already â¦
â¦disabled WAL
You can merge this pull request into a Git repository by running:
$ git pull https://githu
My variant of API avoids cache configuration.
One more thing to note - as we found out control.sh cannot dump XML
configuration. Currently it returns only subset of properties. And in
general case it is impossible to convert CacheConfiguration to Spring XML,
because Spring XMLis not serialization
Sergey Chugunov created IGNITE-10374:
Summary: Node doesn't own rebalanced partitions on rebalancing
finished
Key: IGNITE-10374
URL: https://issues.apache.org/jira/browse/IGNITE-10374
Project: Ign
Vovan,
We couldn't avoid API with cache configuration.
Almost all of ~70 properties could be changed, some of them are instances
of objects or could be user-defined class.
Could you come up with alternatives for user-defined affinity function?
Also, the race would have a place in other scenarios.
It may be OK to extend compatible field types (like from Int to Long).
In Protobuf for example this is allowed just because there is no difference
between Int and Long in binary format: they all are equally varlen encoded
and Longs just will occupy up to 9 bytes, while Ints up to 5.
But for every
Val,
If we treat binary object as a plain container of fields with certain names
and types, we do not care how to convert Int to String. This is up to user
to decide how to migrate.
Ignite could help users in some cases. E.g. for SQL caches we may provide
ALTER TABLE command, which will do necessa
Pavel Konstantinov created IGNITE-10373:
---
Summary: Web console: we need to fix docker-compose.yml
Key: IGNITE-10373
URL: https://issues.apache.org/jira/browse/IGNITE-10373
Project: Ignite
Denis,
Several examples:
1) DEFAULT values - in SQL you may avoid storing default value in the table
and store it in metadata instead. Not applicable for BinaryObject because
the same binary object may be saved to two SQL tables with different
defaults
2) DATE and other temporal types - in SQL you
Ilya,
Currently binary objects already works almost as you proposed. We have 4
bytes types (type name hash) and we have 4 bytes schema ID (hash of all
field names). We do not write field IDs in the object itself. What we do
not have is separation of fixed and varlen fields. Agree, that we should
i
Denis,
Problems with separate parameters are explained above.
чт, 22 нояб. 2018 г. в 3:23, Denis Magda :
> Vladimir,
>
> All of the alternatives are reminiscent of mathematical operations. Don't
> look like a SQL command. What if we use a SQL approach introducing named
> parameters:
>
> KILL QUE
Ed,
We may have API similar to “cache” and “getOrCreateCache”, or may not. It
is up to us to decide. Similarity on it’s own is weak argument.
Functionality and simplicity - this is what matters.
Approach with cache configuration has three major issues
1) It exposes properties which user will not
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 finalize
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 finalize
We should definitely allow to change type of field/column to another
compatible type. The fact that we do not allow to change Int to Long is
pretty insane. However, there are cases when it's much more complicated.
How are we going to replace Int with a String, for example? I believe this
should req
Vladimir,
Could you educate me a little bit, why the current format is bad for SQL
and why another one is more suitable?
Also, if we introduce the new format then why would we keep the binary one?
Is the new format just a next version of the binary one.
2.3) Remove restrictions on changing field
Vladimir,
All of the alternatives are reminiscent of mathematical operations. Don't
look like a SQL command. What if we use a SQL approach introducing named
parameters:
KILL QUERY query_id=10 [AND node_id=5]
--
Denis
On Wed, Nov 21, 2018 at 4:11 AM Vladimir Ozerov
wrote:
> Denis,
>
> Space is
Vovan,
Would you argue that we should have the similar API in Java as
Ignite.cache(CacheConfiguration) or
Ignite.getOrCreateCache(CacheConfiguration)?
With a proposed solution, every other API call would rely on it finally.
I am interested in having such feature not arguing about API alternative
Dmitriy Pavlov created IGNITE-10372:
---
Summary: [TC Bot] Optimize master trends page
Key: IGNITE-10372
URL: https://issues.apache.org/jira/browse/IGNITE-10372
Project: Ignite
Issue Type: Tas
GitHub user antonovsergey93 opened a pull request:
https://github.com/apache/ignite/pull/5467
Ignite 2.5.1 p161
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p161
Alternatively you can revie
GitHub user xtern reopened a pull request:
https://github.com/apache/ignite/pull/5466
Ignite 1793 test mass run.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-1793
Alternatively you can review and apply the
Github user xtern closed the pull request at:
https://github.com/apache/ignite/pull/5466
---
Hi Andrey,
Thank you for bringing this question to the list. I already reviewed this
PR and it looks good to me. But I would like to hear more opinions from
other community members regarding the whole approach.
One important detail - we are going to create new suites as a child classes
of existin
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4835
---
Hi Igniters,
For a long time, I did not collect MTCGA reports because now we have a very
convenient statistics page for the Bot ( https://goo.gl/4Tj1mo ).
But today I've decided to check our progress since August. As always you
can find full test report from 30 latest runs here
https://cwiki.apac
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5458
---
Aleksey Zinoviev created IGNITE-10371:
-
Summary: [ML] Add multiple metrics calculation fo Binary
Classification Evaluation process
Key: IGNITE-10371
URL: https://issues.apache.org/jira/browse/IGNITE-10371
asfgit closed pull request #77: IGNITE-10336: Build chain collection refactored
to avoid missing builds
URL: https://github.com/apache/ignite-teamcity-bot/pull/77
This is an automated message from the Apache Git Service.
To
Hi,
Vladimir, Ilya,
What about variable length fields? How do you suggest to store offsets in
footer or header?
For large objects, headers will allow to retrive field faster and detect
null immediately, but we have to reserve place for all var-len fields
offset and update header after serializa
GitHub user xtern opened a pull request:
https://github.com/apache/ignite/pull/5466
Ignite 1793 test mass run.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-1793
Alternatively you can review and apply these
Ed,
Why do we want to operate on CacheConfiguration so desperately? Your
example raises even more questions:
1) What to do with thin clients?
2) What to do with aforementioned race conditions, when cache could be
changed concurrently?
3) Why such trivial operation from user perspective is only sup
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/5465
ignite-8765: Fixed forgotten import.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8765-fix-imports
Al
By the very first look, a new method can work absolutely the same with
cache() & getOrCreateCache() - it will be easy to follow by users.
Vladimir, could you give an example of API you proposing to implement?
ср, 21 нояб. 2018 г. в 19:32, Eduard Shangareev :
> Vovan,
>
> user already is able to
Vovan,
user already is able to get cache configuration as xml.
control.sh --cache list '.' --config
So, user could update it and run:
control.sh --cache --restart -cfg=xml.path
On Wed, Nov 21, 2018 at 7:06 PM Vladimir Ozerov
wrote:
> Ed,
>
> He can do that programmatically. But I meant anothe
Hello!
I would like to propose the following changes:
- Let's allow multiple BinaryType's per Class. Make typeId = cksum(list of
class types + fields) as opposed of cksum(class name) as we have it
currently. Note that we only have to compute that once per class loaded in
JVM.
- BinaryType has a l
Ed,
He can do that programmatically. But I meant another case - Java node
creates a cache. Then .NET node wants to change it. Proposed API cannot
handle it.
ср, 21 нояб. 2018 г. в 19:03, Eduard Shangareev :
> Vladimir,
>
> I didn't get how does .Net user start caches right now? XML and remote
>
Vladimir,
I didn't get how does .Net user start caches right now? XML and remote
node? Right?
On Wed, Nov 21, 2018 at 6:55 PM Vladimir Ozerov
wrote:
> Ed,
>
> We are not Java product. We support 6 platforms at the moment. Why do we
> implement a feature which can only be used in Java, when it
Ed,
We are not Java product. We support 6 platforms at the moment. Why do we
implement a feature which can only be used in Java, when it is very easy to
make it available from everywhere?
ср, 21 нояб. 2018 г. в 18:50, Eduard Shangareev :
> Vladimir,
>
> It would be Java API specific.
> For a use
asfgit closed pull request #76: IGNITE-10275 Refactor of visa caching.
URL: https://github.com/apache/ignite-teamcity-bot/pull/76
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreig
Vladimir,
It would be Java API specific.
For a user, we would add a new command for console.sh which would take an
XML-file path as a parameter.
We could add other possibilities: for example, with the builder which would
finally call this Ignite.restartCaches method. But it's nice to have, not a
Ed,
Could you please demonstrate how .NET node or .NET will change cache
configuration with proposed API? Taking in count that XML is not available
in most cases, and custom Java classes from cache configuration are
available only on server nodes and only from Java.
ср, 21 нояб. 2018 г. в 18:36,
Vladimir,
I don't see any difference here.
The same possibilities would be available as with normal cache start:
-XML;
-remote node.
>3) Avoid race condition when configuration changes between configuration
read and method call (what could lead to a number of strange effects).
Well, we could ad
Ed,
Caches in .NET could be started programmatically, from XML which .NET API
has no access to, or dynamically from remote nodes (eg Java node).
ср, 21 нояб. 2018 г. в 18:24, Eduard Shangareev :
> Vladimir,
>
> How does .Net user start caches right now?
>
> On Wed, Nov 21, 2018 at 6:10 PM Vladim
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5396
---
Vladimir,
How does .Net user start caches right now?
On Wed, Nov 21, 2018 at 6:10 PM Vladimir Ozerov
wrote:
> Eduard,
>
> Simple != correct. Let’s consider a simple use case: user want to change
> PARTITIONED -> REPLICATED from .NET, but do not some classes from
> CacheConfiguration. How do we
Correction: “do not *have* some classes”.
ср, 21 нояб. 2018 г. в 18:09, Vladimir Ozerov :
> Eduard,
>
> Simple != correct. Let’s consider a simple use case: user want to change
> PARTITIONED -> REPLICATED from .NET, but do not some classes from
> CacheConfiguration. How do we solve this?
>
> Vlad
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/5464
IGNITE-9902: ScanQuery doesn't take lost partitions into account
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite igni
GitHub user SomeFire opened a pull request:
https://github.com/apache/ignite/pull/5463
IGNITE-10301 GridToStringBuilder is broken for classes with inheritance
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SomeFire/ignite IGNITE
Alex,
Spring XML is not easily available from API. Sometimes it simply doesn’t
exist.
Why not use builder instead?
Ignite.changeCache(“my_cache”,
Builder.create().setCacheMode(REPLICATED).build())
Advantages:
1) Available on all platforms
2) Expose only properties we support
3) Avoid race condit
Vova, Ed
I think in case when classes not available we can sent a string with cache
XML configuration (bean) to server node that has all classes in classpath.
What do you think?
On Wed, Nov 21, 2018 at 10:10 PM Vladimir Ozerov
wrote:
> Eduard,
>
> Simple != correct. Let’s consider a simple use
zzzadruga opened a new pull request #78: IGNITE-10203 Support for alternative
configurations for PR testing
URL: https://github.com/apache/ignite-teamcity-bot/pull/78
This is an automated message from the Apache Git Service.
Eduard,
Simple != correct. Let’s consider a simple use case: user want to change
PARTITIONED -> REPLICATED from .NET, but do not some classes from
CacheConfiguration. How do we solve this?
Vladimir.
ср, 21 нояб. 2018 г. в 18:02, Eduard Shangareev :
> Vladimir,
>
> I propose not to change cache
dspavlov opened a new pull request #77: IGNITE-10336: Build chain collection
refactored to avoid missing builds
URL: https://github.com/apache/ignite-teamcity-bot/pull/77
This is an automated message from the Apache Git Serv
Vladimir,
I propose not to change cache configuration in runtime but restart cache
with the new compatible configuration on data which we have underfoot.
What we could change:
-backup count;
-TRANSACTIONAL <-> ATOMIC;
-REPLICATED - PARTITIONED;
-other settings.
So, yeah, it would be great to hav
Hi Igniters,
As you may already know, MVCC transaction feature will be available in
upcoming Ignite-2.7.
However, MVCC Tx feature is released for beta testing and has many
limitations and we a going
to improve stability and integrations with other features in future
releases.
We can reuse existed
Eduard,
Got it. Please take the following things in count during design:
1) Two distinct PMEs might not work well. Consider a situation w1hen I
decided to move a cache with index "MY_INDEX" from schema A to schema B.
While cache was stopped, another cache with index "MY_INDEX" was created in
sche
Possibly heading into wishlist rather than practical territory here, but you
did ask...
> What we need is to introduce an interface which will convert a pair of
> key-value objects into a row. This row will be used to store data and to
> get fields from it.
Rather than mapping objects to a row,
Sure. thanks for the reply. I think in this case we should mention a new
method in all error messages like 'cache create failed because of different
configs'.
So a user can easily find a new method to apply. So product will point
itself to a method how to get the evolution of cache configs without
Makes sense.
I'm trying to grasp this from usability POV.
Having two ways of storing data with different behavior can be confusing.
In .NET we already have this issue with DateTime when if you want SQL, you
get subtly different behavior.
So IMO we should enable strict type checks for all caches,
Dmitriy,
>From my point of view, it's not good to have such unexpected behavior (and
change old one) for cache and getOrCreateCache method.
It should be a conscious decision, not an accident.
On Wed, Nov 21, 2018 at 5:01 PM Eduard Shangareev
wrote:
> Vladimir,
>
> 1) Affinity could be changed,
Vladimir,
1) Affinity could be changed, but count of partition couldn't be.
2) So it would trigger 2 PME. Dynamic start and stop.
3) In theory, should cancel them and new setting should be applied. How it
works now? Create an index and stop node, for example.
On Wed, Nov 21, 2018 at 4:56 PM Vladi
GitHub user ibessonov opened a pull request:
https://github.com/apache/ignite/pull/5462
IGNITE-10369 PDS 4 hangs on TC
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10369
Alternatively you can rev
Hi Eduard,
Can we just change cache parameters after calling cache() or
getOrCreateCache() by user? The method is blocked until restart finished.
We can set up new cache parameters according to the provided configuration.
If it is not possible to change some parameter, a method will fail.
I gues
Hi Ed,
Several questions from my side:
1) If we do not allow to change the most demanded by users things like
affinity or persistence/in-memory, then what kind of configuration
properties do we expect to be changed? Can we have several examples?
2) How will it interact with PME?
3) How will it int
Hi Vishwas,
Are you going to do some contribution related to your question? If not
then you could ask the same question on u...@ignite.apache.org User
list exists exactly for asking questions related to usability problems
and most likely you will get an answer there.
ср, 21 нояб. 2018 г. в 10:26,
Igniters,
I propose new public API to change the cache configuration of persistent
caches with keeping data.
It would look like:
Ignite ignite = ...;
ignite.restartCaches(cfg1, ... cfgN);
where cfgX is a new cache configuration, which contains the name of an
existing persistent cache.
The obvi
Hi Taras,
Unfortunately, this will not be easy to implement. We already have
AffinityTopologyVersion which is updated on certain schema change
operations, such as CREATE/DROP TABLE. Moreover, it is already passed in
query request messages (GridH2QueryRequest.topVer). Unfortunately, it is
not updat
Hi Vyacheslav, Vladimir,
Could you please invite me, if you will set up a call.
ср, 21 нояб. 2018 г. в 13:08, Vladimir Ozerov :
> Hi Vyacheslav,
>
> Still not clear enough for me. I do not see a reason to send another over a
> ring in case of successful execution. The only reason is an error on
Hi Peter,
I am not aware of such ticket.
On Wed, Nov 21, 2018 at 2:23 PM Peter Borissow
wrote:
> Hello Vladimir,Is there a ticket for the issue I described in JIRA or
> should we create one and mark it blocked pending #6173?
>
> Thanks,Peter
>
> On Wednesday, November 21, 2018, 3:30:21
Pavel,
This could be solved with aforementioned "RowFormat". We will be able to
configure cache as follows: "this is a cache with strict type checks, first
one is A, with fields A1, A2, A3, second is B with fields B1, B2". So it
will be possible to serialize anything into binary object, but when i
Vladimir,
The query protocol will be changed in both solution.
The tables versions must be added to the 'GridQueryNextPageResponse'
message
and must be compared on the reduce node too. Because the DLL / DML race
may be happens on different nodes.
21.11.2018 15:24, Vladimir Ozerov пишет:
Tara
Github user oleg-ostanin closed the pull request at:
https://github.com/apache/ignite/pull/4812
---
GitHub user dmitrievanthony opened a pull request:
https://github.com/apache/ignite/pull/5461
IGNITE-10370: Fix TensorFlowLocalInferenceExample fail on Windows
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignit
Anton Dmitriev created IGNITE-10370:
---
Summary: ML: TensorFlowLocalInferenceExample fails on Windows
Key: IGNITE-10370
URL: https://issues.apache.org/jira/browse/IGNITE-10370
Project: Ignite
SomeFire commented on a change in pull request #76: IGNITE-10275 Refactor of
visa caching.
URL: https://github.com/apache/ignite-teamcity-bot/pull/76#discussion_r235369867
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/visa/TcBotTriggerAndSignOffService
SomeFire commented on a change in pull request #76: IGNITE-10275 Refactor of
visa caching.
URL: https://github.com/apache/ignite-teamcity-bot/pull/76#discussion_r235369173
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/db/TcHelperDb.java
##
@@ -93,6
SomeFire commented on a change in pull request #76: IGNITE-10275 Refactor of
visa caching.
URL: https://github.com/apache/ignite-teamcity-bot/pull/76#discussion_r235369350
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/db/TcHelperDb.java
##
@@ -93,6
Ivan Bessonov created IGNITE-10369:
--
Summary: PDS 4 hangs on TC
Key: IGNITE-10369
URL: https://issues.apache.org/jira/browse/IGNITE-10369
Project: Ignite
Issue Type: Test
Reporte
Taras,
Thank you for analysis. I'd like to add that there is another solution -
PME :-) In this case DDL will be blocked until current SELECTs and updates
are finished, and do not allow new operations to be executed. This approach
solves all issues - it avoids deadlocks between query threads and D
Please start a vote according to
https://www.apache.org/foundation/voting.html
Anyone can start a vote, you don't need to be a PMC.
I don't feel it is a very important issue to remove notifications from the
list, as it can be easily filtered out using mail setup. But if someone
feels it is really
Congratulations, Igor!
On Wed, Nov 21, 2018 at 10:11 AM Alexey Zinoviev
wrote:
> Great news, Igor, hope to use this great feature in ML module!
>
> вт, 20 нояб. 2018 г. в 11:08, Павлухин Иван :
>
> > Igor my congratulations! Keep going!
> >
> > 2018-11-20 9:01 GMT+01:00, Vladimir Ozerov :
> > >
Andrew Mashenkov created IGNITE-10368:
-
Summary: MVCC: Create "Cache 9" test suite for MVCC mode.
Key: IGNITE-10368
URL: https://issues.apache.org/jira/browse/IGNITE-10368
Project: Ignite
Andrew Mashenkov created IGNITE-10367:
-
Summary: MVCC: Create "Cache 8" test suite for MVCC mode.
Key: IGNITE-10367
URL: https://issues.apache.org/jira/browse/IGNITE-10367
Project: Ignite
Vladimir,
IMO the issue is that we allow any type of data in the cache (put Person,
then put int to the same cache).
Are we going to address this in 3.0 and enforce key/value types according
to cache configuration?
This will provide more space for optimizations.
On Wed, Nov 21, 2018 at 3:14 PM Vl
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5057
---
Andrew Mashenkov created IGNITE-10366:
-
Summary: MVCC: Create "Cache 1" test suite for MVCC mode.
Key: IGNITE-10366
URL: https://issues.apache.org/jira/browse/IGNITE-10366
Project: Ignite
Andrew Mashenkov created IGNITE-10365:
-
Summary: MVCC: Create "Cache 6" test suite for MVCC mode.
Key: IGNITE-10365
URL: https://issues.apache.org/jira/browse/IGNITE-10365
Project: Ignite
Denis,
In theory data conversion could be avoided in certain cases. E.g. consider
a case of loading data through streamer. We know the cache, we know it's
metadata and row format. So instead of doing "user object" -> "binary
object" -> "row", we can do "user object" -> "row".
On Wed, Nov 21, 2018
Denis,
Space is bad candidate because it is a whitespace. Without whitespaces we
can have syntax without quotes at all. Any non-whitespace delimiter will
work, though:
KILL QUERY 45.1
KILL QUERY 45-1
KILL QUERY 45:1
On Wed, Nov 21, 2018 at 3:06 PM Юрий wrote:
> Denis,
>
> Let's consider parame
Denis,
Let's consider parameter of KILL QUERY just a string with some query id,
without any meaning for user. User just need to get the id and pass as
parameter to KILL QUERY command.
Even if query is distributed it have single query id from user perspective
and will killed on all nodes. User jus
GitHub user oignatenko opened a pull request:
https://github.com/apache/ignite/pull/5460
IGNITE-10191 Incorrect comparison of lists in
RendezvousAffinityFunctionSimpleBenchmark#testAffinityCompatibility
You can merge this pull request into a Git repository by running:
$ git p
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/5459
IGNITE-8391
Removing some WAL history segments leads to WAL rebalance hanging
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache
Congratulations!
On Wed, Nov 21, 2018 at 12:30 PM Dmitriy Pavlov wrote:
> Congrats, Pavel. Well deserved achievement.
>
> ср, 21 нояб. 2018 г., 12:09 Nikita Amelchev :
>
> > Congratulations, Pavel!
> > ср, 21 нояб. 2018 г. в 11:47, Vyacheslav Daradur :
> > >
> > > Congrats Pavel, I'm looking for
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5412
---
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/5458
IGNIE-10339 Fix connection to cluster failed when invoking
validate indexes closure from control.sh
You can merge this pull request into a Git repository by running:
$ git pull https://githu
Hi community,
We will enhance lazy mode for SQL query execution.
Lazy mode overview:
Lazy mode is related to H2 lazy mode when the all query results are not
copied to the RAM in some cases.
The mode it is applicable for SELECTs that doesn't not require
materialize all results in memory, e.g.
Hello Vladimir, Is there a ticket for the issue I described in JIRA or
should we create one and mark it blocked pending #6173?
Thanks,Peter
On Wednesday, November 21, 2018, 3:30:21 AM EST, Vladimir Ozerov
wrote:
Hi Peter,
We will be able to fix this in consistent way for both "th
Vyacheslav Koptilin created IGNITE-10364:
Summary: .Net: FailureHandlerTest should be reworked
Key: IGNITE-10364
URL: https://issues.apache.org/jira/browse/IGNITE-10364
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5430
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5415
---
Pavel Konstantinov created IGNITE-10363:
---
Summary: Web console: unexpected unsaved changes confirmation
Key: IGNITE-10363
URL: https://issues.apache.org/jira/browse/IGNITE-10363
Project: Ignite
1 - 100 of 140 matches
Mail list logo
