Alex Savitsky created IGNITE-11806:
--
Summary: Wrong import statement listed in Scalar documentation
Key: IGNITE-11806
URL: https://issues.apache.org/jira/browse/IGNITE-11806
Project: Ignite
Alexandr Shapkin created IGNITE-11805:
-
Summary: .NET runnable core executable
Key: IGNITE-11805
URL: https://issues.apache.org/jira/browse/IGNITE-11805
Project: Ignite
Issue Type: New
Alexei Scherbakov created IGNITE-11804:
--
Summary: Assertion error
Key: IGNITE-11804
URL: https://issues.apache.org/jira/browse/IGNITE-11804
Project: Ignite
Issue Type: Bug
Stanilovsky Evgeny created IGNITE-11803:
---
Summary: Re-balancing is cancelled if client node joins,
reinvestigate.
Key: IGNITE-11803
URL: https://issues.apache.org/jira/browse/IGNITE-11803
Hi Saikat and Ivan,
I think that properties that related to SQL should not be configured on
caches.
We already put a lot of effort to decouple SQL from caches.
I think we should develop some kind of "Queries" options on Ignite
configuration.
What do you think?
On Wed, Apr 24, 2019 at 3:22 PM
Congratulations, Ivan!
On Wed, Apr 24, 2019 at 10:50 AM Dmitriy Pavlov wrote:
> Dear Apache Ignite Developers,
>
>
> The Project Management Committee (PMC) for Apache Ignite has invited Ivan
> Pavlukhin to become a committer and we are pleased to announce that he has
> accepted.
>
>
>
> Ivan
Ok, I created a ticket [1].
After TC Bot visa I'll let you know that ticket is ready for review in Jira.
[1] https://issues.apache.org/jira/browse/IGNITE-11802
ср, 24 апр. 2019 г. в 11:08, Павлухин Иван :
> Hi Ivan,
>
> Thank you for a quick response! Looks like that
> keepSerializedObjects()
Ivan Fedotov created IGNITE-11802:
-
Summary: Check keepSerializedObjects() condition after each test
Key: IGNITE-11802
URL: https://issues.apache.org/jira/browse/IGNITE-11802
Project: Ignite
Hi Saikat,
I think that we should have a discussion and choose a place where a
"default query timeout" property will be configured.
Generally, I think that a real (user) problem is possibility for
queries to execute indefinitely. And I have no doubts that we can
improve there. There could be
Hi Ivan,
Thank you for a quick response! Looks like that
keepSerializedObjects() is the cause. Yes, please create a ticket. Do
not hesitate to ping me if any assistance is needed.
ср, 24 апр. 2019 г. в 10:54, Ivan Fedotov :
>
> Hi, Dmitry
>
> I took a look at failures and it could be caused by
Hi, Dmitry
I took a look at failures and it could be caused by changes in
tearDown/clearTestEnviroment method. In the latest master version before
IGNITE-11412 serializedObj.clear(); will be invoked only if
(!keepSerializedObjects()) condition will be satisfied [1].
So the insertion of this
Dear Apache Ignite Developers,
The Project Management Committee (PMC) for Apache Ignite has invited Ivan
Pavlukhin to become a committer and we are pleased to announce that he has
accepted.
Ivan contributes a lot into community development by being very active on
the user and dev lists. He
Ivan Fedotov & Ivan Pavluchin could you please take a look at these
failures?
ср, 24 апр. 2019 г. в 02:05, :
> 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
Alexei Scherbakov created IGNITE-11801:
--
Summary: Clearing of moving partition may lead to partition desync.
Key: IGNITE-11801
URL: https://issues.apache.org/jira/browse/IGNITE-11801
Project:
Alexei Scherbakov created IGNITE-11800:
--
Summary: Update counters in
o.a.i.i.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl#update
could be applied from stale messages
Key: IGNITE-11800
Alexei Scherbakov created IGNITE-11799:
--
Summary: Do not always clear partition in MOVING state before
exchange
Key: IGNITE-11799
URL: https://issues.apache.org/jira/browse/IGNITE-11799
Project:
16 matches
Mail list logo