Evgeniy Rudenko created IGNITE-13259:
Summary: "default" cache usage should be removed from REST API
Key: IGNITE-13259
URL: https://issues.apache.org/jira/browse/IGNITE-13259
Project: Ignite
Hi Ilya,
Thank you for your reply. I will check if I can recover the nightly
artifact publish job.
Regards,
Saikat
On Mon, Jul 13, 2020 at 6:00 AM Ilya Kasnacheev
wrote:
> Hello!
>
> We used to publish nightlies to some non-main repo but I'm afraid this may
> be broken currently.
>
> Regards,
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New test failure in master-nightly
IgfsLocalSecondaryFileSystemDualAsyncSelfTest.testAccessAndModificationTimeUpwardsPropagation
Igniters,
I've made an important change to the IEP (and the POC):
OP_QUERY_CONTINUOUS_END_NOTIFICATION is another client -> server message
that notifies the client that the query has stopped and no more events
should be expected.
This is important because client can't immediately stop listening
I don't think it's required to wait until Ignite 3.0 to make this happen.
If I'm not mistaken, we stopped releasing Hadoop binaries and sources a
long time ago (at least you can't longer find them on the downloads page).
Also, we removed all the mentioning from the documentation and website.
Hi Max,
Could you check if the EVT_CACHE_QUERY_EXECUTED event is what you're
looking for?
https://www.gridgain.com/docs/latest/developers-guide/events/events#cache-query-events
-
Denis
On Fri, Jul 10, 2020 at 3:54 AM Max Timonin wrote:
> Hi Igniters!
>
> We're going to protocol all input SQL
This might be a topic for Ignite 3.0, but I do agree that the ability to
create custom node filters is unnecessary and error-prone. Attribute-based
filtering should be more than enough.
-Val
On Tue, Jul 14, 2020 at 3:15 AM Pavel Tupitsyn wrote:
> Alex,
>
> Thank you for diving into this.
>
Vladimir Goncharov created IGNITE-13258:
---
Summary: Improve control.sh --cache list command to show cache
sizes
Key: IGNITE-13258
URL: https://issues.apache.org/jira/browse/IGNITE-13258
Project:
Alex, i also suggest to merge this
https://issues.apache.org/jira/browse/IGNITE-13229 too, GridClient leakage and
further TC OOM preventing.
>Ivan,
>
>It was already in release scope as discussed in this thread.
>
>вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com >:
>
>>
Maksim Timonin created IGNITE-13257:
---
Summary: Kubernetes example is not working
Key: IGNITE-13257
URL: https://issues.apache.org/jira/browse/IGNITE-13257
Project: Ignite
Issue Type: Bug
Sergey Uttsel created IGNITE-13256:
--
Summary: IgniteCacheNearRestartRollbackSelfTest.testRestarts
(Cache restarts) (Regression) became flaky
Key: IGNITE-13256
URL:
I've removed Initial Query from the POC and IEP (left a note there about
the decision).
Since there are no other comments and concerns, I'll move on with the final
implementation.
On Fri, Jul 10, 2020 at 4:14 PM Pavel Tupitsyn wrote:
> Igor, Alex,
>
> I was aware of the duplicates issue with
Hi guys,
I want to implement a more honest heuristic for historical rebalance.
Before, a cluster makes a choice between the historical rebalance or not it
only from a partition size. This threshold more known by a name of property
IGNITE_PDS_WAL_REBALANCE_THRESHOLD.
It might prevent a historical
Vladislav Pyatkov created IGNITE-13254:
--
Summary: Historical rebalance iterator may skip checkpoint if it
not contains updates
Key: IGNITE-13254
URL: https://issues.apache.org/jira/browse/IGNITE-13254
Christian Ehrlicher created IGNITE-13255:
Summary: ODBC/JDBC is very slow
Key: IGNITE-13255
URL: https://issues.apache.org/jira/browse/IGNITE-13255
Project: Ignite
Issue Type: Bug
Vladislav Pyatkov created IGNITE-13253:
--
Summary: Advanced heuristics for historical rebalance
Key: IGNITE-13253
URL: https://issues.apache.org/jira/browse/IGNITE-13253
Project: Ignite
Alex,
Thank you for diving into this.
Indeed, custom node filters seem to have some issues.
1. For .NET, I'm fairly certain that we don't need custom node filters.
Let's just make AttributeNodeFilter available natively (as a .NET class).
2. For Java, we should at least fix the "call filter on
Hi,
I'm working on adding the NodeFilter functionality to the .NET client
https://issues.apache.org/jira/browse/IGNITE-2890
And there are several points I want to highlight regarding the current
implementation:
1) A node filter is being called on every put which seems redundant. This
might be
Ivan,
It was already in release scope as discussed in this thread.
вт, 14 июл. 2020 г. в 14:31, Ivan Rakov :
> Hi,
>
> We are still waiting for a final review of Tracing functionality [1] until
> the end of tomorrow (July 15).
> We anticipate that it will be merged to Ignite master no later
Hi,
We are still waiting for a final review of Tracing functionality [1] until
the end of tomorrow (July 15).
We anticipate that it will be merged to Ignite master no later than July 16.
Sorry for being a bit late here. Alex P., can you include [1] to the
release scope?
[1]:
Igniters,
The PR is ready to be merged, all comments from my side have been fixed.
If anyone has more comments, please let know today.
Best Regards,
Ivan Rakov
On Tue, Jun 30, 2020 at 10:43 AM Alexander Lapin
wrote:
> Hello Igniters,
>
> I'd like to discuss with you and then donate changes
21 matches
Mail list logo
