Hello, Denis.
> Nickolay, as for that fork which is in GG codebase - GridGain is a major
> contributor and maintainer but the others are welcomed to send
> pull-requests.
Can we make this fork maintained by Ignite Community?
With all respect to Grid Gain as an author of Apache Ignite I don't lik
Anton Vinogradov created IGNITE-11971:
-
Summary: Consistency check on test finish
Key: IGNITE-11971
URL: https://issues.apache.org/jira/browse/IGNITE-11971
Project: Ignite
Issue Type: Tas
Hi,
I made some small improvements in JdkMarshaller [1]. I will be happy
if someone reviews it. Changes are quite simple.
[1] https://issues.apache.org/jira/browse/IGNITE-11951
--
Best regards,
Ivan Pavlukhin
Hen,
Ignite community knows that the changes will be available under non-Apache
2.0 license and doesn't see this as a showstopper for contribution. Some
community members will be contributing to the H2 fork owned by the
community. The question is where can we host this fork. If the fork can be
loc
Hi Nikita,
I've checked out your branch, looked through the changes and run
IgniteBaselineNodeLeaveExchangeTest. Some thoughts:
1. First of all, there's fundamental issue that backup and primary
partitions behave differently:
- On primary, updating transaction needs to own exclusive lock (be
My bad, I've sent the message accidentally. What I wanted to ask:
Alex S,
backups that are promoted to primaries without global synchronization
are not affected by transactional load
test still fails with LWM > HWM assertion
Do you have any ideas why this may happen?
New primary node should
Hi Nikita,
I've checked out your branch, looked through the changes and run
IgniteBaselineNodeLeaveExchangeTest. Some thoughts:
1. First of all, there's fundamental issue that backup and primary
partitions behave differently:
- On primary, updating transaction needs to own exclusive lock (be
Hi Denis,
from SO question and https://issues.apache.org/jira/browse/IGNITE-11970
ticket description it seems to me it is not platform/.NET specific.
According to issue description proposed fix is not looking as overly
complex. May be ticket reporter can provide a fix and run TC (since there
is s
Hi,
I'm not aware of such plans, for now.
Maybe SQL experts (CCed) can provide some more details.
Sincerely,
Dmitriy Pavlov
вс, 7 июл. 2019 г. в 15:39, liyuj <18624049...@163.com>:
> Hi,
>
> Is Ignite planning to support COMMENT ON statements?
>
> H2 supports this command.
> If Ignite can supp
Pavel, Igor, Aleksandr,
Could you please check this thread:
https://stackoverflow.com/questions/56803904/java-outofmemoryexception-when-using-continuous-query-in-ignite
Here is a related ticket: https://issues.apache.org/jira/browse/IGNITE-11970
Is it easy to implement this optimization? Can
There is the "ignite-dev" user that manages Nubble forums linked to the dev
list:
http://apache-ignite-developers.2346864.n4.nabble.com/template/NamlServlet.jtp?macro=user_nodes&user=1
Do you we know a password used for that account? Dmitry, is it in that
passwords page available for the PMC group
The modifications to the H2 source would need to be published under
"MPL-2.0", "EPL-1.0", or "(MPL-2.0 OR EPL-1.0)". I don't believe there
would be interest in publishing ASF-community authored source under a
different license than Apache 2.0.
Hen
On Tue, Jul 9, 2019 at 12:50 PM Denis Magda wrot
Adding a valid legal mailing list.
-
Denis
On Tue, Jul 9, 2019 at 12:46 PM Denis Magda wrote:
> Apache Ignite's SQL engine is tightly coupled with the H2 database engine
> [1] that provides basic parsing and query execution capabilities.
>
> H2 is licensed under dual MPL 2.0 and EPL 1.0 [2], t
Apache Ignite's SQL engine is tightly coupled with the H2 database engine
[1] that provides basic parsing and query execution capabilities.
H2 is licensed under dual MPL 2.0 and EPL 1.0 [2], thus Ignite community
uses H2 binary artifacts for the development needs and doesn't have H2
source code in
Igniters,
I made a PR for metrics configuration.
Please, review
https://github.com/apache/ignite/pull/6676/files
В Вт, 09/07/2019 в 12:27 +0300, Nikolay Izhikov пишет:
> Hello, Alex.
>
> OK, Let's go with the simplest solution.
> I will provide API and JMX method for metrics configuration shor
Igor Belyakov created IGNITE-11970:
--
Summary: Excessive use of memory in continuous queries
Key: IGNITE-11970
URL: https://issues.apache.org/jira/browse/IGNITE-11970
Project: Ignite
Issue Ty
Hello, Alex.
OK, Let's go with the simplest solution.
I will provide API and JMX method for metrics configuration shortly.
В Пн, 08/07/2019 в 18:23 +0300, Alexey Goncharuk пишет:
> Nikolay,
>
> To me a separate metrics configuration file seems to be not very
> user-friendly. First of all, it doe
Anton Kalashnikov created IGNITE-11969:
--
Summary: Incorrect DefaultConcurrencyLevel value in .net test
Key: IGNITE-11969
URL: https://issues.apache.org/jira/browse/IGNITE-11969
Project: Ignite
Stanislav Lukyanov created IGNITE-11968:
---
Summary: FailureProcessor reports tcp-comm-worker as blocked when
resolving communication errors in ZK
Key: IGNITE-11968
URL: https://issues.apache.org/jira/browse/I
19 matches
Mail list logo
