Denis,
Java thin client is in the final review stage - I expect it will go to
master sometime next week. April 30 release date seems to have enough
contingency for this component.
Thanks!
Alexander Kalinin created IGNITE-8028:
-
Summary: Implement unit test for reseting password.
Key: IGNITE-8028
URL: https://issues.apache.org/jira/browse/IGNITE-8028
Project: Ignite
Issue
I’ll do my best to deliver packages in time.
Concerning Java 9/10 — AFAIK there are limitations how do we support it:
* compilation is supported with scala_2.10 modules switched off (due to scala
support Java 9 itself starting from 2.12.x+ versions);
* also compilation and run is possible only
Vladimir,
As SQL expert, could you review this PR?
In this PR QueryEntity.java was changed. And it may impact whole SQL engine.
--
Alexey Kuznetsov
Dmitriy,
Thank you for a hint. Please find below a link to new TeamCity run. This
time looks much better but still has a lot of failed tests. But most of
them not related to my changes except failed .Net tests. Can you please
review and advise on next steps?
Thanks,
Amir
Valentin Kulichenko created IGNITE-8027:
---
Summary: Expired entry appears back in case of node restart with
persistence enabled
Key: IGNITE-8027
URL: https://issues.apache.org/jira/browse/IGNITE-8027
Nikolay,
Sounds like a good idea. I will do my best to speed up the process and
review asap.
-Val
On Thu, Mar 22, 2018 at 11:37 AM, Nikolay Izhikov
wrote:
> Hello, guys
>
> I agree with earlier release.
>
> I propose to include my task IGNITE-7077 to 2.5 release.
>
>
I agree that compute and services functionality is important for thin
client. It doesn't seem to be very hard to implement, but would provide
much better flexibility, as users would be able to do remote invocation of
arbitrary code, use collocated processing, etc. Having an ability to do
this from
Hi Igniters,
Why not? Let's release it a bit earlier.
I think it would be good if Ivan will prepare fix for WAL LOG_ONLY:
http://apache-ignite-developers.2346864.n4.nabble.com/Reconsider-default-WAL-mode-we-need-something-between-LOG-ONLY-and-FSYNC-td28165.html
Ivan, what do you think?
Also it
Also, we has new API - ContinuousQueryWithTransformer merged for 2.5 release -
[IGNITE-425]
В Чт, 22/03/2018 в 21:37 +0300, Nikolay Izhikov пишет:
> Hello, guys
>
> I agree with earlier release.
>
> I propose to include my task IGNITE-7077 to 2.5 release.
>
> Valentin, do you have a time slot
Hi all!
Dmitriy thank you for review.
I`ve just fixed all your comments.
чт, 22 мар. 2018 г. в 20:36, Dmitry Pavlov :
> HI Dmitriy, thank you!
>
> Roman, could you please address Dmitriy's comments?
>
> чт, 22 мар. 2018 г. в 19:18, Дмитрий Рябов :
Ilya,
That's outstanding research and summary. Thanks for spending your time on
this.
Not sure I have enough expertise to challenge your approach, but it sounds
100% reasonable to me. As side notes:
- Don't you want to aggregate the tickets under an IEP?
- Does it mean we're going to
Hello, guys
I agree with earlier release.
I propose to include my task IGNITE-7077 to 2.5 release.
Valentin, do you have a time slot to review my implementation?
В Чт, 22/03/2018 в 10:39 -0700, Denis Magda пишет:
> Igniters,
>
> According to our regular schedule, every new Ignite version
Igniters,
Is anybody working on this bug? There is a high chance we can add a fix to
2.5 if the community agrees to release it earlier.
--
Denis
On Thu, Mar 15, 2018 at 11:04 AM, Denis Magda wrote:
> I dared to set fix version to 2.5 and increased the severity. It's
>
Denis,
Do we really need to measure cache sizes precisely? We can use approach 1
and also we have average pagesFillFactor metric. These two metrics can give
a good estimation of page memory size per cache.
2018-03-22 21:04 GMT+03:00 Denis Magda :
> Igniters,
>
> Glad to see
Petr,
Java Thin client, GA Grid, COPY command are the most significant additions
to the release (if to talk about the features). Aside from that, I see many
valuable optimizations and fixes that have been sitting in the master for a
while (some of them were merged in January). It's preferable to
Igniters,
Glad to see that 2.4 made it possible to show memory usage in bytes for
data regions. Good progress but it's definitely not enough.
I'd like to discuss how we can support "memory usage per cache/table" in
bytes. That's actually what the users are interested in. Talking to Alex G.
we
Will there be a major new feature or this release will concentrate on stability
and optimisations?
Also, I guess, we will have to include into 2.5 release full support for Java 9
and Java 10 (that WILL require some developers time).
And RPM / DEB packages stage II phase will require lots of
Igniters,
According to our regular schedule, every new Ignite version usually goes
public once in 3 months. As you remember, the latest 2.4 release, which
took us 5 months to improve and roll out, was based on the version of the
source code dated by January.
Since that time the master branch
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/3686
IGNITE-8018 : Optimized initialValue(...)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8018
Alternatively
Of course, I check every new build several times until it gives the same
results as obsolete one.
> On 22 Mar 2018, at 19:44, Dmitry Pavlov wrote:
>
> Hi Petr,
>
> This is an important change in Ignite's testing process. Current and future
> Igniters will be grateful
Hi Petr,
This is an important change in Ignite's testing process. Current and future
Igniters will be grateful for this change.
However, there may be a failure in tests 1) that were previously disabled
or 2) new infrastucture-related failures.
Any assistance with the identification each of type
Igniters,
As you may noticed, main test project is undergoing some refactoring;
namely, we are moving to architecture which is designed to reduce full tests
run time by introducing 'single-build / multiple tests' scheme: Apache
Ignite is built once and its artifacts are used in later parallel
HI Dmitriy, thank you!
Roman, could you please address Dmitriy's comments?
чт, 22 мар. 2018 г. в 19:18, Дмитрий Рябов :
> Hi Dmitriy,
>
> I took a look for PR, it needs codestyle fixes.
>
> 2018-03-19 14:22 GMT+03:00 Dmitry Pavlov :
>
>> Hi Alexey,
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/3685
IGNITE-8019 : Optimized checkpointReadLock acquisition during rebalancing.
You can merge this pull request into a Git repository by running:
$ git pull
Hi Dmitriy,
I took a look for PR, it needs codestyle fixes.
2018-03-19 14:22 GMT+03:00 Dmitry Pavlov :
> Hi Alexey,
>
> Did you find the patch is looking good and is ready to be merged?
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 15 мар. 2018 г. в 11:19, Alexey Kukushkin
Anton Kalashnikov created IGNITE-8026:
-
Summary: Deadlock in TxDeadlockDetectionTest.testNoHangs
Key: IGNITE-8026
URL: https://issues.apache.org/jira/browse/IGNITE-8026
Project: Ignite
Andrey Kuznetsov created IGNITE-8025:
Summary: Result of GridTestUtils.runMultiThreadedAsync has a bug
in cancel() implementation
Key: IGNITE-8025
URL: https://issues.apache.org/jira/browse/IGNITE-8025
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/3684
IGNITE-7712 Server-side system property IGNITE_SQL_FORCE_LAZY_RESULT_SET
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Igniters,
I've spent some time analyzing performance of rebalancing process. The
initial goal was to understand, what limits it's throughput, because it is
significantly slower than network and storage device can theoretically
handle.
Turns out, our current implementation has a number of issues
I have created pull requests for both of tickets.
https://github.com/apache/ignite/pull/3651/files please comment if you have
strong reservations against this usability fix.
Note that it doesn't change timeouted get() behaviour because we can't know
in advance how long flush() will take.
--
Taras Ledkov created IGNITE-8024:
Summary: Enhance JDBC logging
Key: IGNITE-8024
URL: https://issues.apache.org/jira/browse/IGNITE-8024
Project: Ignite
Issue Type: Task
Components:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3677
---
Stanislav Lukyanov created IGNITE-8023:
--
Summary: Processors are incorrectly initialized if during a node's
reconnection cluster changes its state
Key: IGNITE-8023
URL:
Ivan,
How quick are you going to merge the fix into the master? Many persistence
related optimizations have already stacked up. Probably, we can release
them sooner if the community agrees.
--
Denis
On Thu, Mar 22, 2018 at 5:22 AM, Ivan Rakov wrote:
> Thanks all!
> We
Github user daradurvs closed the pull request at:
https://github.com/apache/ignite/pull/3635
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3578
---
Github user daradurvs closed the pull request at:
https://github.com/apache/ignite/pull/3653
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2382
---
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/3683
IGNITE-7904: Changed IgniteUtils::cast not to trim exception chains.
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/3204
---
Ksenia Rybakova created IGNITE-8022:
---
Summary: Need to add README.txt for ignite-direct-io
Key: IGNITE-8022
URL: https://issues.apache.org/jira/browse/IGNITE-8022
Project: Ignite
Issue
Vladislav Pyatkov created IGNITE-8021:
-
Summary: Destroyed caches can be return to life by restart grid
Key: IGNITE-8021
URL: https://issues.apache.org/jira/browse/IGNITE-8021
Project: Ignite
Ilya Lantukh created IGNITE-8020:
Summary: Rebalancing for persistent cache should transfer file
store over network instead of using existing supply/demand protocol
Key: IGNITE-8020
URL:
Ilya Lantukh created IGNITE-8019:
Summary: During rebalancing checkpoint read lock is acquired for
each entry (twice).
Key: IGNITE-8019
URL: https://issues.apache.org/jira/browse/IGNITE-8019
Project:
GitHub user aealeksandrov opened a pull request:
https://github.com/apache/ignite/pull/3682
IGNITE-7902 Enable either swap space or persistence but not both
Enabling both swap and persistence at the same time for a data region does
not make sense. An exception should be thrown in
Ilya Lantukh created IGNITE-8018:
Summary: Avoid unnecessary unswap(...) call in
GridCacheMapEntry.initialValue(...)
Key: IGNITE-8018
URL: https://issues.apache.org/jira/browse/IGNITE-8018
Project:
Ilya Lantukh created IGNITE-8017:
Summary: Disable WAL during initial preloading
Key: IGNITE-8017
URL: https://issues.apache.org/jira/browse/IGNITE-8017
Project: Ignite
Issue Type:
Thanks all!
We seem to have reached a consensus on this issue. I'll just add
necessary fsyncs under IGNITE-7754.
Best Regards,
Ivan Rakov
On 22.03.2018 15:13, Ilya Lantukh wrote:
+1 for fixing LOG_ONLY. If current implementation doesn't protect from data
corruption, it doesn't make sence.
+1 for fixing LOG_ONLY. If current implementation doesn't protect from data
corruption, it doesn't make sence.
On Wed, Mar 21, 2018 at 10:38 PM, Denis Magda wrote:
> +1 for the fix of LOG_ONLY
>
> On Wed, Mar 21, 2018 at 11:23 AM, Alexey Goncharuk <
>
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/3681
IGNITE-7871 2-phase wait for partition release (Validate update counters)
You can merge this pull request into a Git repository by running:
$ git pull
Congratulations!
Such an impressive amount of work in such a short time!
Thanks,
Amir
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/2949
---
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/3160
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3483
---
Hi Amir,
It seems reason was compilation error
Compilation error: Compiler
Compilation failure
/data/teamcity/work/bd85361428dcdb1/modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/IgniteSqlCaseInsensitiveTest.java:[614,23]
cannot find symbol
symbol: method
Yakov,
DiscoveryWorker is critical worker itself and could be terminated or
blocked by user provided listener. So specific abstraction for failure
handling is more robust way to solve the problem because it doesn't
dependent on other components.
On Tue, Mar 20, 2018 at 1:33 PM, Yakov Zhdanov
It works, thanks!
Here is updated links for Artifacts and Changes respectively with silent guest
login (can be added to bookmarks):
*
https://ci.ignite.apache.org/viewLog.html?buildId=lastSuccessful=Releases_NightlyRelease_RunApacheIgniteNightlyRelease=artifacts=1
*
Alexander Paschenko created IGNITE-8016:
---
Summary: Make sure checks in QueryUtils.typeForQueryEntity are sane
Key: IGNITE-8016
URL: https://issues.apache.org/jira/browse/IGNITE-8016
Project:
Pavel Konstantinov created IGNITE-8015:
--
Summary: NPE on adding node to baseline
Key: IGNITE-8015
URL: https://issues.apache.org/jira/browse/IGNITE-8015
Project: Ignite
Issue Type: Bug
I have turned on access to guest user.
Check pls.
On 22 March 2018 at 12:10, Petr Ivanov wrote:
> I’ve added corresponding role to guest access user.
>
> Vitaly, can you open Ignite Apache TC for guest login if no security
> issues exists that prevent from opening it?
GitHub user ekaterina-nbl opened a pull request:
https://github.com/apache/ignite/pull/3680
IGNITE-8014 Node.js client: basic/minimal version
for initial review/feedback
You can merge this pull request into a Git repository by running:
$ git pull
Alexey Kosenchuk created IGNITE-8014:
Summary: Node.js client: basic/minimal version
Key: IGNITE-8014
URL: https://issues.apache.org/jira/browse/IGNITE-8014
Project: Ignite
Issue Type:
Igor Sapego created IGNITE-8013:
---
Summary: CPP: Check pending snapshots in
BinaryTypeManager::GetHandler
Key: IGNITE-8013
URL: https://issues.apache.org/jira/browse/IGNITE-8013
Project: Ignite
Alexander Kalinin created IGNITE-8011:
-
Summary: Fix E2E tests
Key: IGNITE-8011
URL: https://issues.apache.org/jira/browse/IGNITE-8011
Project: Ignite
Issue Type: Bug
Igor Sapego created IGNITE-8012:
---
Summary: CPP: BinaryWriter::WriteElement should accept const
reference instead of value.
Key: IGNITE-8012
URL: https://issues.apache.org/jira/browse/IGNITE-8012
I’ve added corresponding role to guest access user.
Vitaly, can you open Ignite Apache TC for guest login if no security issues
exists that prevent from opening it?
> On 22 Mar 2018, at 11:49, Alexey Kuznetsov wrote:
>
> +1 to get nightly builds WITHOUT login.
>
> On
+1 to get nightly builds WITHOUT login.
On Thu, Mar 22, 2018 at 3:38 PM, Dmitriy Setrakyan
wrote:
> Why do we need to ask people to login to get a nightly build? Anyway to
> open it to public without a login?
>
>
--
Alexey Kuznetsov
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/3679
-
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-4756
Alternatively you can review and apply these changes as the
Why do we need to ask people to login to get a nightly build? Anyway to
open it to public without a login?
On Wed, Mar 21, 2018 at 10:45 PM, Dmitry Pavlov
wrote:
> Hi Raymond,
>
> You could sign up using valid email address. Please write to @dev list if
> link still is
Dmitriy, congratulations on getting the committer stripes! The Apache
Ignite community got much better and more organized since you joined it,
and the initiatives like "Make TeamCity green again" continue to improve
the quality of our project. Please keep it up.
D.
On Thu, Mar 22, 2018 at 1:33
GitHub user dmekhanikov opened a pull request:
https://github.com/apache/ignite/pull/3678
Ignite 2.4.4.b1 build
Created for testing
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.4.b1
Denis Mekhanikov created IGNITE-8010:
Summary: Validate marshaller mappings on join
Key: IGNITE-8010
URL: https://issues.apache.org/jira/browse/IGNITE-8010
Project: Ignite
Issue Type:
Hi, Igniters!
Look like it's outdated and can be closed.
Could someone comment if this ticket [1] is still valid?
[1] https://issues.apache.org/jira/browse/IGNITE-4662
On Wed, Jun 28, 2017 at 2:38 AM, Valentin Kulichenko
wrote:
> I'm not sure this ticket is
Congrats!
Best Regards,
Ivan Rakov
On 22.03.2018 10:08, Vyacheslav Daradur wrote:
Congrats, Dmitry, great work!
On Thu, Mar 22, 2018 at 10:06 AM, Petr Ivanov wrote:
Congratulations, Dmitry!
On 22 Mar 2018, at 01:33, Denis Magda wrote:
The
Congrats, Dmitry, great work!
On Thu, Mar 22, 2018 at 10:06 AM, Petr Ivanov wrote:
> Congratulations, Dmitry!
>
>
>
>> On 22 Mar 2018, at 01:33, Denis Magda wrote:
>>
>> The Project Management Committee (PMC) for Apache Ignite
>> has invited Dmitry Pavlov
Congratulations, Dmitry!
> On 22 Mar 2018, at 01:33, Denis Magda wrote:
>
> The Project Management Committee (PMC) for Apache Ignite
> has invited Dmitry Pavlov to become a committer and we are pleased
> to announce that he has accepted.
>
> Dmitriy is an active member of
Yes, will do.
чт, 22 мар. 2018 г. в 1:05, Denis Magda :
> Dmitriy,
>
> Thanks for updating the WAL section. Now it makes total sense to me.
>
> As for the page with JNA projects, let's get added there! Could you
> contact the owners?
>
> --
> Denis
>
>
> On Wed, Mar 21, 2018
78 matches
Mail list logo