Github user xtern closed the pull request at:
https://github.com/apache/ignite/pull/5466
---
Sergi,
I think we should not guess for users what is right or wrong for them. It
is up to user to decide what is valid. For example, consider a user who
operates on a list of Integers, and to optimize memory consumption he
decide to save in the same field either List, or plain Integer in
case only
Ryabov Dmitrii created IGNITE-10375:
---
Summary: Fix inspection failures
Key: IGNITE-10375
URL: https://issues.apache.org/jira/browse/IGNITE-10375
Project: Ignite
Issue Type: Bug
Hi Igor Seliverstov,
I can see some test is failed with issue link
https://issues.apache.org/jira/browse/IGNITE-10104
Could you please mute test on TC as well?
Sincerely,
Dmitriy Pavlov
чт, 22 нояб. 2018 г. в 07:21, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled.
GitHub user SomeFire opened a pull request:
https://github.com/apache/ignite/pull/5469
IGNITE-10375 Fix inspection failures
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SomeFire/ignite IGNITE-10375
Alternatively you can revie
GitHub user dmelnichuk opened a pull request:
https://github.com/apache/ignite/pull/5470
IGNITE-10358
Fixes a Collection-related bug in Python thin client.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nobitlost/ignite ignite-10
I don't see how you variant handles user-defined objects (factories,
affinity-functions, interceptors, etc.). Could you describe?
On Thu, Nov 22, 2018 at 10:47 AM Vladimir Ozerov
wrote:
> My variant of API avoids cache configuration.
>
> One more thing to note - as we found out control.sh cannot
Guys,
I like the idea with the configuration builder more.
We could limit the set of properties by providing only modifiable ones in
the builder interface.
Otherwise only runtime will show whether you tried to modify a proper
setting.
And if we decide to make another property modifiable, then we w
Ed,
We have ~70 properties in CacheConfiguration. ~50 of them are plain, ~20
are custom classes. My variant allows to change plain properties from any
platform, and the rest 20 from any platform when user has relevant
BinaryType.
On Thu, Nov 22, 2018 at 11:30 AM Eduard Shangareev <
eduard.shangar
If we are developing a product for users, we already guessing what is right
and what is wrong for them. So let's avoid these sophistic statements.
In the end it is always our responsibility to provide a balanced set of
trade-offs between
usability, performance and safety.
Let me repeat, I'm not a
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/5471
IGNITE-10216: disable sort annotations in inspection config
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite ignite-10216
Alternat
Actually, option with separate parameters was mentioned in another thread
http://apache-ignite-developers.2346864.n4.nabble.com/proposed-design-for-thin-client-SQL-management-and-monitoring-view-running-queries-and-kill-it-tp37713p38056.html
Denis
чт, 22 нояб. 2018 г. в 08:51, Vladimir Ozerov :
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/5472
-
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-9023
Alternatively you can review and apply these changes as the p
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/5076
---
Ivan Fedotov created IGNITE-10376:
-
Summary: NPE during invocation from cache
Key: IGNITE-10376
URL: https://issues.apache.org/jira/browse/IGNITE-10376
Project: Ignite
Issue Type: Test
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/5473
IGNITE-9171 Use lazy mode for default
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9171
Alternative
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5353
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5461
---
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5474
IGNITE-10050: MVCC: Create "Cache 5" test suite for MVCC mode.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
Andrew Mashenkov created IGNITE-10377:
-
Summary: MVCC: Incorrect exception is thrown if no data nodes
found for a partition.
Key: IGNITE-10377
URL: https://issues.apache.org/jira/browse/IGNITE-10377
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/5475
IGNIE-10339 Skip index partition file integrity check for in-memory
caches.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ig
dspavlov opened a new pull request #79: IGNITE-10372: Optimize master trends
page, fast fix
URL: https://github.com/apache/ignite-teamcity-bot/pull/79
This is an automated message from the Apache Git Service.
To respond to t
Igor Seliverstov created IGNITE-10378:
-
Summary: MVCC TX: Possible race on MVCC coordinator reassignment
Key: IGNITE-10378
URL: https://issues.apache.org/jira/browse/IGNITE-10378
Project: Ignite
asfgit closed pull request #79: IGNITE-10372: Optimize master trends page, fast
fix
URL: https://github.com/apache/ignite-teamcity-bot/pull/79
This is an automated message from the Apache Git Service.
To respond to the messa
Hi, Igniters!
Here is Jira issue [1] to drop one of Ignite's system property
"IGNITE_SERVICES_COMPATIBILITY_MODE" because it is not used.
I looked through git history and related Jira issues, the common conclusions:
- the property was introduced in Ignite 1.7 within the task [2] to use
LazyServic
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/5476
IGNITE-10323 Contol utility --deactivate on non-activate cluster prodâ¦
â¦use NPE and handler stop nodes
You can merge this pull request into a Git repository by running:
$ git pull https
GitHub user Rodion4ik opened a pull request:
https://github.com/apache/ignite/pull/5477
IGNITE-8558 Provide an opportunity to stop grids and cancel tasks after
execution all tests
Add method to class GridAbstractTest
Add new boolean method "isWillJobsCancelled()" which can be ov
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5478
IGNITE-10365: MVCC: Create "Cache 6" test suite for MVCC mode.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/5479
IGNITE-10329: query and query-join benchmarks for Ignite, Postgresql and
Mysql
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgai
Hi,
Lets discuss changes of Ignite public interface relates to retry SQL
queries.
Should we add new public exception (.e.g: `QueryRetryException`) for
cache SQL API
and special vendor error code to SQLException for JDBC?
21.11.2018 16:32, Vladimir Ozerov пишет:
Hi Taras,
Unfortunately, th
Vladimir Ozerov created IGNITE-10379:
Summary: SQL: Extract partition info from BETWEEN and range
conditions for integer types
Key: IGNITE-10379
URL: https://issues.apache.org/jira/browse/IGNITE-10379
Vyacheslav,
You are right. This property is not used anywhere, so you can safely remove
it.
I don't think, there is any need in deprecation. You can just go ahead and
drop it,
since it doesn't have any effect.
Denis
чт, 22 нояб. 2018 г. в 15:47, Vyacheslav Daradur :
> Hi, Igniters!
>
> Here is
dspavlov opened a new pull request #80: IGNITE-10372 Step 2 In memory caching
of build statistics, don't loading tests for composite
URL: https://github.com/apache/ignite-teamcity-bot/pull/80
This is an automated message fro
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/5480
Ignite 2.7 master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.7-master
Alternatively you can review and app
asfgit closed pull request #80: IGNITE-10372 Step 2 In memory caching of build
statistics, don't loading tests for composite
URL: https://github.com/apache/ignite-teamcity-bot/pull/80
This is an automated message from the Ap
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5352
---
Alexey Goncharuk created IGNITE-10381:
-
Summary: U.doInParallel can terminate early due to an error in
batch processing
Key: IGNITE-10381
URL: https://issues.apache.org/jira/browse/IGNITE-10381
Pr
Aleksey Zinoviev created IGNITE-10380:
-
Summary: [ML] Drop Multi-label Classification for Logistic
Regression and SVM
Key: IGNITE-10380
URL: https://issues.apache.org/jira/browse/IGNITE-10380
Proj
GitHub user zaleslaw opened a pull request:
https://github.com/apache/ignite/pull/5481
IGNITE-9145: Added EncodingSortingStrategy
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9145
Alternatively y
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5369
---
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/5482
IGNITE-7441 Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-7
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/5483
IGNITE-10381 Fixed U.doInParallel early termination
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10381
Alt
GitHub user artemmalykh opened a pull request:
https://github.com/apache/ignite/pull/5484
IGNITE-10272: Inject learning environment into scope of dataset compute
task.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apa
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5460
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4882
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5469
---
Yury Babak created IGNITE-10382:
---
Summary: [ML] Move datasets from example to ml module
Key: IGNITE-10382
URL: https://issues.apache.org/jira/browse/IGNITE-10382
Project: Ignite
Issue Type: Imp
Github user Jokser closed the pull request at:
https://github.com/apache/ignite/pull/5450
---
Max Shonichev created IGNITE-10383:
--
Summary: Partition Full message finished info printed out in logs
after full message sent info
Key: IGNITE-10383
URL: https://issues.apache.org/jira/browse/IGNITE-10383
Sergey Antonov created IGNITE-10384:
---
Summary: Stop caches in parallel
Key: IGNITE-10384
URL: https://issues.apache.org/jira/browse/IGNITE-10384
Project: Ignite
Issue Type: Improvement
Anton Kurbanov created IGNITE-10385:
---
Summary: NPE in CachePartitionPartialCountersMap.toString
Key: IGNITE-10385
URL: https://issues.apache.org/jira/browse/IGNITE-10385
Project: Ignite
Iss
dspavlov opened a new pull request #81: IGNITE-10372 Optimize master trends
page step 3: Tests migrated to new concept
URL: https://github.com/apache/ignite-teamcity-bot/pull/81
This is an automated message from the Apache
Github user ibessonov closed the pull request at:
https://github.com/apache/ignite/pull/4768
---
Ivan Rakov created IGNITE-10386:
---
Summary: Add mode when WAL won't be disabled during rebalancing
caused by BLT change
Key: IGNITE-10386
URL: https://issues.apache.org/jira/browse/IGNITE-10386
Project:
Ivan Rakov created IGNITE-10387:
---
Summary: Enable IgniteNodeAttributes#ATTR_MACS_OVERRIDE attribute
in basic TC suites
Key: IGNITE-10387
URL: https://issues.apache.org/jira/browse/IGNITE-10387
Project:
Stepan,
Thank you for your great job in evaluating Python thin client, as well
as other thin clients.
There was indeed a bug in Python client regarding the handling of type
hints in Collection type. I created a fix and did a PR under
IGNITE-10358 task, but the same PR is also fixes the probl
Sergey Karpushin created IGNITE-10388:
-
Summary: Prevent Ignite from "dying" if first attempt to join the
cluster failed
Key: IGNITE-10388
URL: https://issues.apache.org/jira/browse/IGNITE-10388
P
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
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
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
Hi,
May be I am a little bit late with my thoughts about a command syntax.
How do I see it is going to be used:
1. A user is able to kill a query by unique id belonging only to this query.
2. A user is able to kill all queries started by a specific node.
For killing a single query we must identify
Hi Vladimir,
How do you see a default tablespace configuration in the "bright"
future? Is it going to be a single file for an Ignite instance? In
what cases will be there benefits to explicitly configure additional
tablespaces?
By the way was the name "tablespace" hand-crafted or it was it
borrowe
65 matches
Mail list logo
