Kirill Tkalenko created IGNITE-11995:
Summary: control.sh if experimental command disabled - don't show
help for experemental commands
Key: IGNITE-11995
URL: https://issues.apache.org/jira/browse/IGNITE-11995
JSR107 point - it is standard, it is always easy to refer to something user
may already know.
BTW we have 1.0 in Ignite dependency, 1.1.1 recently released, maybe we
should upgrade in 3.0.
See also:
https://mvnrepository.com/artifact/javax.cache/cache-api/1.1.1
ср, 17 июл. 2019 г. в 15:51, Vyac
Dmitriy Pavlov created IGNITE-11994:
---
Summary: [TC Bot] Prepare new view to select base branch and other
build parameters
Key: IGNITE-11994
URL: https://issues.apache.org/jira/browse/IGNITE-11994
Pr
Kirill Tkalenko created IGNITE-11993:
Summary: Print warning if awaiting next wal segment it too long
Key: IGNITE-11993
URL: https://issues.apache.org/jira/browse/IGNITE-11993
Project: Ignite
FYI,
Build configuration PdsIndexingWalRecovery was removed.
ср, 17 июл. 2019 г. в 14:31, Павлухин Иван :
>
> Yet another candidate
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_QueriesOom?branch=pull%2F4611%2Fhead&buildTypeTab=overview
>
> ср, 17 июл. 2019 г. в 14:06, Павл
Stepachev Maksim created IGNITE-11992:
-
Summary: Improvements for new security approach
Key: IGNITE-11992
URL: https://issues.apache.org/jira/browse/IGNITE-11992
Project: Ignite
Issue Typ
Hello, Igniters.
The main idea of the new security is propagation security context to
other nodes and does action with initial permission. The solution looks
fine but has imperfections.
1. ZookeaperDiscoveryImpl doesn't implement security into itself.
As a result: Caused by: class org.apach
Ivan,
* About Service Grid:
Yes, we discussed that old service grid implementation
(GridServiceProcessor) should be removed in 3.0, now it is marked as
obsolete.
This was in the list, maybe it was lost during formatting.
Also, a class `ServiceConfiguration` should be moved to common package
of co
Also, I did not quite get the point about JSR107 (JCache). From time
to time I see on user-list threads where Ignite is used along with
Spring annotation-based cache integration. I suppose it requires
JCache interfaces. What is crucially wrong with supporting it?
ср, 17 июл. 2019 г. в 15:19, Павлу
Folks,
Sorry if I am repeating something. I checked a page [1] and have not
found several items.
1. I thought that there was an agreement of dropping OLD service grid,
was not it?
2. Also IndexingSpi seems to me as a candidate for removal.
Should I add those items to the page? Or is there another
Pavel Kuznetsov created IGNITE-11991:
Summary: [TC Bot]: Rerun possible blockers sets incorrect "SCALE
FACTOR" build parameter
Key: IGNITE-11991
URL: https://issues.apache.org/jira/browse/IGNITE-11991
Hello Anton,
It's not possible, currently, to fix atomic caches.
> You may only check the consistency. *And it's better than nothing*, I
> think.
Fair enough.
>> 3. IgniteConsistencyViolationException is absolutely useless. It does not
> >> provide any information about the issue and possible wa
Yet another candidate
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_QueriesOom?branch=pull%2F4611%2Fhead&buildTypeTab=overview
ср, 17 июл. 2019 г. в 14:06, Павлухин Иван :
>
> Here is a closed PR [1]. Let's drop that run-config [2].
>
> [1] https://github.com/apache/ignite/pul
Here is a closed PR [1]. Let's drop that run-config [2].
[1] https://github.com/apache/ignite/pull/4239/files
[2]
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PdsIndexingWalRecovery?branch=%3Cdefault%3E&buildTypeTab=overview
чт, 21 мар. 2019 г. в 17:53, Petr Ivanov :
>
> A
Vladimir Malinovskiy created IGNITE-11990:
-
Summary: Optimize heap usage for TcpDiscoveryNodeAddedMessage
stored in pending messages in ServerImpl
Key: IGNITE-11990
URL: https://issues.apache.org/jira/brow
Maxim Muzafarov created IGNITE-11989:
Summary: Preload predicate not used in GridCachePreloader
Key: IGNITE-11989
URL: https://issues.apache.org/jira/browse/IGNITE-11989
Project: Ignite
I
Hi Ivan,
Please see the thread `Removal of TC Run Configuration
PdsIndexingWalRecovery`
https://lists.apache.org/thread.html/ad0b3b69c1ddf637e817f35b34e3f117e6565c38522d030e86e0e773@%3Cdev.ignite.apache.org%3E
Since nobody came there, I guess it is ok to just remove it.
Sincerely,
Dmitriy Pavlo
Kirill Tkalenko created IGNITE-11988:
Summary: control.sh validate_indexes SQL Index issue add
information about group and cache id
Key: IGNITE-11988
URL: https://issues.apache.org/jira/browse/IGNITE-11988
Hi,
Does anyone know what is the purpose of job PDS (Indexing / WAL &
Recovery) [1]? It refers to non-existing
IgnitePdsWithIndexingWalAndRecoveryTestSuite class and runs no tests.
Can we delete it safely?
[1]
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PdsIndexingWalRecov
Nikolay Izhikov created IGNITE-11987:
Summary: [IEP-35] Add ability to configure metrics
Key: IGNITE-11987
URL: https://issues.apache.org/jira/browse/IGNITE-11987
Project: Ignite
Issue Ty
20 matches
Mail list logo
