Github user pavlukhin closed the pull request at:
https://github.com/apache/ignite/pull/5042
---
Pavel Konstantinov created IGNITE-9967:
--
Summary: Web console: an error in browser console on opepning
Readme.txt in Project Structure modal
Key: IGNITE-9967
URL:
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
Mikhail Cherkasov created IGNITE-9966:
-
Summary: Dump configuration to distinct file and all dynamic
changes to the cluster
Key: IGNITE-9966
URL: https://issues.apache.org/jira/browse/IGNITE-9966
Mikhail Cherkasov created IGNITE-9965:
-
Summary: Ignite.sh must enable GC logs by default
Key: IGNITE-9965
URL: https://issues.apache.org/jira/browse/IGNITE-9965
Project: Ignite
Issue
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5040
---
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/5054
IGNITE-9964: Added test.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9964
Alternatively you can review and
GitHub user ascherbakoff opened a pull request:
https://github.com/apache/ignite/pull/5053
IGNITE-8873 Preload cache partition into page memory.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8873
Hello, Igniters.
As you may know, we successfully implement TDE. Phase-1 feature. [1]
This improvement allows users to use an encrypted cache.
To make TDE production ready I propose to extend it with two things:
* Master key rotation.
* Cache key rotation.
Such features
GitHub user ibessonov opened a pull request:
https://github.com/apache/ignite/pull/5052
IGNITE-9915 Do not block get/getAll during baseline node stopping.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5041
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4968
---
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/5051
IGNITE-6811: Allowed empty batch in JDBC thin driver.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Github user AMashenkov closed the pull request at:
https://github.com/apache/ignite/pull/5029
---
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/5050
IGNITE-9962 Complete cache start future with error if register metadaâ¦
â¦ta was failed
You can merge this pull request into a Git repository by running:
$ git pull
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4752
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5034
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5004
---
GitHub user antonovsergey93 opened a pull request:
https://github.com/apache/ignite/pull/5049
IGNITE-9963 Wraps quotes path to mvn command
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9963
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4926
---
Stanislav Lukyanov created IGNITE-9964:
--
Summary: SQL: query by affinity key fails when a table is created
from a custom template
Key: IGNITE-9964
URL: https://issues.apache.org/jira/browse/IGNITE-9964
GitHub user SomeFire opened a pull request:
https://github.com/apache/ignite/pull/5048
IGNITE-9961 GridMessageListenSelfTest#testNullTopic() duplicates
#testNonNullTopic()
You can merge this pull request into a Git repository by running:
$ git pull
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4931
---
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/5047
IGNITE-9957 Updates count was reduced to speed up the test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4969
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5005
---
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/5046
IGNITE-9959: Set consistent id in tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9959
Alternatively
Hi, Dmitrii!
As for [1], I think your suggestion is good to complete the change.
As for [2], I tend to disagree: in future tests default no-op handler can
hide bugs of new Ignite functionality. If it is really needed, developer
can explicitly mention that critical failure is a normal part of
I tried to replace default no-op handler by handler stopping node and
failing the test.
I've returned the no-op handler in many classes because critical
situations are expected behavior. But PR still have a lot of failed
tests and suites. In some tests, I can't understand a failure reason.
I'm
Sergey Antonov created IGNITE-9963:
--
Summary: Tests with mvn command invocation failed if path to
M2_HOME contains spaces.
Key: IGNITE-9963
URL: https://issues.apache.org/jira/browse/IGNITE-9963
Hi,
It seems it is not stable but very often failure of the flaky test.
Igniters, could you please take a look if we need so often failed test.
Sincerely,
Dmitriy Pavlov
сб, 20 окт. 2018 г. в 22:30, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled. You are more
Anton Kalashnikov created IGNITE-9962:
-
Summary: Unhandled exception during BatchCacheChangeRequest
Key: IGNITE-9962
URL: https://issues.apache.org/jira/browse/IGNITE-9962
Project: Ignite
Ryabov Dmitrii created IGNITE-9961:
--
Summary: GridMessageListenSelfTest#testNullTopic() duplicates
#testNonNullTopic()
Key: IGNITE-9961
URL: https://issues.apache.org/jira/browse/IGNITE-9961
Hi all,
I also think that abbreviations should not be mandatory (point 3).
But what I am worrying about is a conflict resolution between a patch
submitter and a reviewer.
How to come to an agreement when one side is strictly for and another side
is strictly against
using abbreviations in some
Peter, thanks! Looks good.
Dmitriy, I agree with your proposal. Making community aware sounds the most
important thing, especially for "heavy" builds.
And we can omit any approval to avoid unnecessary slowdown of the
development process.
пн, 22 окт. 2018 г. в 10:41, Petr Ivanov :
> Ivan,
>
>
>
Vladimir Ozerov created IGNITE-9960:
---
Summary: SQL: Revert and reopen lazy flag optimization
(IGNITE-9171)
Key: IGNITE-9960
URL: https://issues.apache.org/jira/browse/IGNITE-9960
Project: Ignite
Alexey Platonov created IGNITE-9959:
---
Summary: Set consistent id in tests
Key: IGNITE-9959
URL: https://issues.apache.org/jira/browse/IGNITE-9959
Project: Ignite
Issue Type: Improvement
Hello, Stephen.
I suggest thin client deployment as a second option together with existing
integration that use Client Node.
> I’m thinking specifically about better support for Spark Streaming, where the
> lack of continuous query support in thin clients removes a significant
> optimisation
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5026
---
Are you suggesting making the Thin Client deployment an option or as a
replacement for the thick-client? If the latter, do we risk making future
desirable changes more difficult (or impossible)? I’m thinking specifically
about better support for Spark Streaming, where the lack of continuous
Ilya,
Disabling P2P class loading for CQ with *autoUnsubscribe=false* is a
minimum, that should be done.
But it will only solves one of the existing problems.
It's still unclear, how to undeploy such queries.
Continuous queries with *autoUnsubscribe=true* have different semantic with
the ones
Ah, never mind. I found out that I chose the wrong test suite to begin with
on Team City. :-)
On Sun, Oct 21, 2018 at 10:20 PM Michael Fong wrote:
> Hi, all,
>
> I happened to have a fix for IGNITE-7153 and created pull request for it. (
> https://github.com/apache/ignite/pull/5044)
>
> I tried
Sergey Chugunov created IGNITE-9958:
---
Summary: Optimize execution time of
CacheContinuousQueryVariationsTest
Key: IGNITE-9958
URL: https://issues.apache.org/jira/browse/IGNITE-9958
Project: Ignite
Ivan,
Please check dependencies list now.
> On 21 Oct 2018, at 11:39, Dmitriy Pavlov wrote:
>
> Hi Ivan,
>
> I believe every time any suite is added or significantly reconfigured it
> should be mentioned in the dev list.
>
> So we don't need to approve any change by discussion, but keeping
Sergey Chugunov created IGNITE-9957:
---
Summary: Optimize execution time of BinaryMetadataUpdatesFlowTest
Key: IGNITE-9957
URL: https://issues.apache.org/jira/browse/IGNITE-9957
Project: Ignite
45 matches
Mail list logo
