Aleksey Zinoviev created IGNITE-9713:
Summary: [ML] Fix JavaDocs in ML Prerpocessing package
Key: IGNITE-9713
URL: https://issues.apache.org/jira/browse/IGNITE-9713
Project: Ignite
Issue
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4787
---
Vladimir Ozerov created IGNITE-9714:
---
Summary: Document ODBC streaming mode
Key: IGNITE-9714
URL: https://issues.apache.org/jira/browse/IGNITE-9714
Project: Ignite
Issue Type: Task
zzzadruga commented on a change in pull request #20: Ignite 9645
URL: https://github.com/apache/ignite-teamcity-bot/pull/20#discussion_r220834879
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/build/GetBuildTestFailures.java
##
@@ -159,51 +1
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4669
---
GitHub user vveider opened a pull request:
https://github.com/apache/ignite-release/pull/3
IGNITE-7251 Remove term "fabric" from Ignite deliverables
* modified scripts to comply with "fabric" removal
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-release/pull/3
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4763
---
Alexey Goncharuk created IGNITE-9715:
Summary: Document WAL compression level
Key: IGNITE-9715
URL: https://issues.apache.org/jira/browse/IGNITE-9715
Project: Ignite
Issue Type: Task
Alexey Goncharuk created IGNITE-9716:
Summary: Document partition distribution and reset lost partitions
commands of control script
Key: IGNITE-9716
URL: https://issues.apache.org/jira/browse/IGNITE-9716
Aleksey Zinoviev created IGNITE-9717:
Summary: [ML] Add setters methods to Logistic Regression and fix
examples/tests
Key: IGNITE-9717
URL: https://issues.apache.org/jira/browse/IGNITE-9717
Projec
Aleksey Zinoviev created IGNITE-9718:
Summary: [ML] Incorrect JavaDoc in RandomForest
Key: IGNITE-9718
URL: https://issues.apache.org/jira/browse/IGNITE-9718
Project: Ignite
Issue Type: B
GitHub user dmitrievanthony opened a pull request:
https://github.com/apache/ignite/pull/4847
IGNITE-9706: Update ignite-tensorflow to support TensorFlow standalone
client mode
TF_CONFIG variable, make user script to use TF_CLUSTER variable.
You can merge this pull request into a G
GitHub user zaleslaw opened a pull request:
https://github.com/apache/ignite/pull/4848
IGNITE-9718: Fix typo in Random Forest JavaDoc
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9718
Alternative
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4848
---
Hi,
I think we can ignore the failure. This test is reported as a failure
because of strange notification of init method as a standalone test.
Actually, initialization is failed as flaky.
Sincerely,
Dmitriy Pavlov
чт, 27 сент. 2018 г. в 8:31, :
> Hi Igniters,
>
> I've detected some new issue
GitHub user YuriBabak opened a pull request:
https://github.com/apache/ignite/pull/4849
IGNITE-9711: [ML] Remove IgniteThread wrapper from ml examples
Fixed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/YuriBabak/ignite ignite-9
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4813
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4777
---
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4850
IGNITE-9661 Optimize partitions validation
logN removed from complexity.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite i
Stanilovsky Evgeny created IGNITE-9719:
--
Summary: Extra rebalanceThreadPoolSize check on client node.
Key: IGNITE-9719
URL: https://issues.apache.org/jira/browse/IGNITE-9719
Project: Ignite
Alexey Goncharuk created IGNITE-9720:
Summary: Initialize partition free lists lazily
Key: IGNITE-9720
URL: https://issues.apache.org/jira/browse/IGNITE-9720
Project: Ignite
Issue Type: T
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/4851
Ig 7196 changes without master PME optimizations
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite ig-7196-prev
Alternatively you c
Oleg Ignatenko created IGNITE-9721:
--
Summary: NPE in
IgniteAuthenticationProcessor$RefreshUsersStorageWorker.body
Key: IGNITE-9721
URL: https://issues.apache.org/jira/browse/IGNITE-9721
Project: Igni
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4852
IGNITE-5795 Binary metadata is registered during start of cache
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5
Fixed, now the fix is in the ignite-2.7 branch.
ср, 26 сент. 2018 г. в 23:18, Dmitriy Pavlov :
> Oops, my fault. It seems I forgot to cherry-pick to 2.7, but I resolved
> ticket with 2.7 assigned.
>
> I will fix it tomorrow.
>
> ср, 26 сент. 2018 г. в 21:52, Denis Magda :
>
>> Thanks, Pavel and t
GitHub user oignatenko opened a pull request:
https://github.com/apache/ignite/pull/4853
IGNITE-9721 NPE in
IgniteAuthenticationProcessor$RefreshUsersStorageWorker.body
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/ap
SomeFire opened a new pull request #22: IGNITE-9697 [TC Bot] Autocomplete
branch for TC field
URL: https://github.com/apache/ignite-teamcity-bot/pull/22
This is an automated message from the Apache Git Service.
To respond to
Hi, Dmitrii
I want to add information in wiki about new page on Ignite TeamCity Helper
[1]. Could you please grant me these permissions? My id is zzzadruga.
[1] https://mtcga.gridgain.com/comparison.html
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Folks,
I've found in `GridCachePartitionExchangeManager:2684` [1] (master branch)
exchange future wrapped
with double `blockingSectionEnd` method. Is it correct? I just want to
understand this change and
how should I use this in the future.
Should I file a new issue to fix this? I think here `blo
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4854
IGNITE-9561 Parallelize affinity calculation and partitions assignment
during PME
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apac
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4826
---
Maxim,
Thanks for being attentive! It's definitely a typo. Could you please create
an issue?
чт, 27 сент. 2018 г. в 16:00, Maxim Muzafarov :
> Folks,
>
> I've found in `GridCachePartitionExchangeManager:2684` [1] (master branch)
> exchange future wrapped
> with double `blockingSectionEnd` method
Andrew Mashenkov created IGNITE-9722:
Summary: MVCC: Test
CacheMvccTransactionTest.testMvccCoordinatorChangeSimple fails.
Key: IGNITE-9722
URL: https://issues.apache.org/jira/browse/IGNITE-9722
Pr
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4814
---
Hi Nikolai,
sure, you are more than welcome to update AI wiki, not only about TC bot
but about all you need to understand during contributing to Ignite.
I've set needed permissions, please check.
Sincerely,
Dmitriy Pavlov
чт, 27 сент. 2018 г. в 15:44, Nikolai Kulagin :
> Hi, Dmitrii
>
> I want
Maxim Muzafarov created IGNITE-9723:
---
Summary: Critial section should be wrapped correctly for
GridCacheDatabaseSharedManager
Key: IGNITE-9723
URL: https://issues.apache.org/jira/browse/IGNITE-9723
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4829
---
Andrew Mashenkov created IGNITE-9724:
Summary: MVCC SQL: Test
CacheMvccSelectForUpdateQueryAbstractTest.testSelectForUpdateDistributed hangs
sporadically.
Key: IGNITE-9724
URL: https://issues.apache.org/jira/
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4855
IGNITE-9686: forward jvm parameter '-XX:+IgnoreUnrecognizedVMOptions' to
child process for tests
You can merge this pull request into a Git repository by running:
$ git pull https:/
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4855
---
Pavel Kovalenko created IGNITE-9725:
---
Summary: Introduce affinity distribution prototype for equal cache
group configurations
Key: IGNITE-9725
URL: https://issues.apache.org/jira/browse/IGNITE-9725
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4797
---
Alexey Platonov created IGNITE-9726:
---
Summary: GridCacheAbstractFailoverSelfTest may lock all suite on
put/remove cache operations
Key: IGNITE-9726
URL: https://issues.apache.org/jira/browse/IGNITE-9726
GitHub user dgovorukhin opened a pull request:
https://github.com/apache/ignite/pull/4856
IGNITE-9550 ready future exchange actions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9550-dg-2
Alternat
GitHub user SGrimstad opened a pull request:
https://github.com/apache/ignite/pull/4857
IGNITE-9632 implementation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite IGNITE-9632
Alternatively you can review a
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4858
IGNITE-9687: update dependencies
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9687
Alternatively you
Taras Ledkov created IGNITE-9727:
Summary: JDK9/10/11: ignite run script must be works with
JDK9/10/11
Key: IGNITE-9727
URL: https://issues.apache.org/jira/browse/IGNITE-9727
Project: Ignite
Igniters,
Code Freeze date is tomorrow. Bad news is that we still have a number of
important features not-yet-merged (of most important - some MVCC stuff,
TDE, PHP/Python clients). Good news is that we made a good progress with
scope decrease. I propose the following release plan then:
1) By 30 S
Igniters,
Code Freeze date is tomorrow. Bad news is that we still have a number of
important features not-yet-merged (of most important - some MVCC stuff,
TDE, PHP/Python clients). Good news is that we made a good progress with
scope decrease. I propose the following release plan then:
1) By 30 S
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/4859
IGNITE-9726: GridCacheAbstractFailoverSelfTest may lock all suite on
put/remove cache operations
You can merge this pull request into a Git repository by running:
$ git pull https://githu
Please ignore. I missed the branch.
On Thu, Sep 27, 2018 at 5:53 PM Vladimir Ozerov
wrote:
> Igniters,
>
> Code Freeze date is tomorrow. Bad news is that we still have a number of
> important features not-yet-merged (of most important - some MVCC stuff,
> TDE, PHP/Python clients). Good news is t
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4386
---
Taras Ledkov created IGNITE-9728:
Summary: JDK11: external class loader problem
Key: IGNITE-9728
URL: https://issues.apache.org/jira/browse/IGNITE-9728
Project: Ignite
Issue Type: Task
Af
SomeFire closed pull request #22: IGNITE-9697 [TC Bot] Autocomplete branch for
TC field
URL: https://github.com/apache/ignite-teamcity-bot/pull/22
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
A
Anton Kalashnikov created IGNITE-9729:
-
Summary: Ability to start GridQueryProcessor in parallel
Key: IGNITE-9729
URL: https://issues.apache.org/jira/browse/IGNITE-9729
Project: Ignite
Is
Currently, you may ask for a review by mention someone and asking him to
review.
And this approach looks good to me.
In case we'll invent reviewer field who will set the reviewer?
It's NOT ok to set somebody as a reviewer!
You should ask somebody to be a reviewer first.
And in case he agrees he wi
Vova,
Huge +1 to do a stabilization.
--
Alexey Kuznetsov
Hello, Vova.
Thank you for clear release status.
I'm +1 for your proposal.
чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov :
> Vova,
>
> Huge +1 to do a stabilization.
>
>
> --
> Alexey Kuznetsov
>
I agree, and I prefer four weeks for stabilization* (1 Oct - 29 Oct)
Do I understand it correctly: Service Grid is still in scope, isn't it? I
find it very important.
чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov :
> Hello, Vova.
>
> Thank you for clear release status.
> I'm +1 for your proposal
Folks,
The JDK11 TC tests results is not totally OK but look like the most
issues are related to the tests environment.
e.g. properties, path resolving, class loaders etc.
The core functions and core functions of modules works properly (see TC
run [1]).
We have the umbrella ticket [2] to tr
Pat Patterson created IGNITE-9730:
-
Summary: JdbcThinDatabaseMetadata.getTables() is case-sensitive
Key: IGNITE-9730
URL: https://issues.apache.org/jira/browse/IGNITE-9730
Project: Ignite
Iss
Hi Anton,
Thank you for bringing this significant concern here.
I'm going to use this field in total correspondence with assignee field
usage. We don't set assignee unless someone agrees to be a developer for
that feature.
Otherwise, it is better to keep an issue as unassigned. Same implies to t
Our current agreement is that Service Grid is out of scope. This is a huge
feature, which hasn't entered review stage so far, We will not be able to
review/fix/test it properly.
On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov
wrote:
> I agree, and I prefer four weeks for stabilization* (1 Oct - 2
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4734
---
Could you please provide a reference to some thread? Probably I missed it.
чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov :
> Our current agreement is that Service Grid is out of scope. This is a huge
> feature, which hasn't entered review stage so far, We will not be able to
> review/fix/test it
Dmitriy,
This is an outcome of current state of Service Grid - it is not ready. We
never committed to have it to 2.7. Our goal was to try to include it into
2.7.
On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov
wrote:
> Could you please provide a reference to some thread? Probably I missed it.
>
Ok, let's wait for feedback from SG Author(s)/Reviewer(s) first. If it is
not ready, ok. But I thought it is almost done.
I apologize if I missed some discussion (it can happen), but
According to the statement "our current agreement"
I can suspect some members are making some sort of private agree
>
> Denis, as PMC Chair, could you please control, that Service Grid
> inclusion/exclusion is discussed properly according to the Apache Way.
It's fine when committers/contributors have private discussions related to
a feature they've been working on. Not everything should go through the dev
list
Folks,
Please stop looking for enemies everywhere. Just went through this thread
and search for "service" word.
On Thu, Sep 27, 2018 at 7:30 PM Denis Magda wrote:
> >
> > Denis, as PMC Chair, could you please control, that Service Grid
> > inclusion/exclusion is discussed properly according to
I need Vhyacheslav's opinion to be absolutely sure what status is now.
We never committed to dates of release, as well. I don't quite understand
what can mean 'the community committed to doing/releasing something'.
About SG, I also concerned why such a big feature has quite a few
discussions on t
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3467
---
I'm new to Ignite and I would like to join Apache Ignite development.
My JIRA's login is AldoRaine
Thanks Yury, good to know about that!
--
Denis
On Wed, Sep 26, 2018 at 3:49 PM Юрий Бабак wrote:
> Denis,
>
> Thanks for this notice, actually this is some kind of atavism. Run this
> code inside IgniteThread was a requirement when we had a distributed
> matrices. But now all our algorithms bui
Hi Alexander,
I've added you to the list of contributors. Now you can assign an issue to
yourself.
Should you have any question, please do not hesitate to ask.
Welcome to the Apache Ignite Community!
Sincerely,
Dmitriy Pavlov
Couple links that can help you to onboard.
https://cwiki.apache.org/
Welcome, Alexander !
Hi Alexander,
I've added you to the list of contributors. Now you can assign an issue
to
yourself.
Should you have any question, please do not hesitate to ask.
Welcome to the Apache Ignite Community!
Sincerely,
Dmitriy Pavlov
Couple links that can help you to onboard
Andrey Kuznetsov created IGNITE-9731:
Summary: NPE is possible during WAL flushing
Key: IGNITE-9731
URL: https://issues.apache.org/jira/browse/IGNITE-9731
Project: Ignite
Issue Type: Task
Igniters,
I've bumped into a new bug in WAL manager recently, see [1]. It looks
critical enough, and can be a good candidate for fixing before 2.7 release.
Do you agree?
[1] https://issues.apache.org/jira/browse/IGNITE-9731
чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov :
> I need Vhyacheslav's
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4860
IGNITE-9501 Backward compatibility fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-9501-compatibility-fix
Al
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4839
---
Yes, I agree, NPE during WAL flush is definitely a blocker.
It is strange why the current test set did not fail after commit.
чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov :
> Igniters,
>
> I've bumped into a new bug in WAL manager recently, see [1]. It looks
> critical enough, and can be a goo
GitHub user macrergate opened a pull request:
https://github.com/apache/ignite/pull/4861
Ignite 2.5.1 p14
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p14
Alternatively you can review and a
Hi Igniters!
As I have written about Service Grid before [1] I'm finalizing the
solution to be sure that implementation is reliable.
About including it in 2.7, if we talk that code freeze tomorrow then
the solution is not ready to merge yet.
I hope that prereviewers Anton Vinogradov and Nikolay I
Valentin Kulichenko created IGNITE-9732:
---
Summary: Add joins to Spark Dataframe examples
Key: IGNITE-9732
URL: https://issues.apache.org/jira/browse/IGNITE-9732
Project: Ignite
Issue Ty
Hi,
I'm grateful for contributions made in that area, but it seems folks don't
have time to fix the test.
Tomorrow I'm going to revert commit.
It seems it is the only way we can keep master more or less green.
https://ci.ignite.apache.org/viewLog.html?buildId=1888723&tab=buildChangesDiv&buildT
Hi,
Are you talking about 'IgniteConfigurationParityTest#TestIgniteConfiguration'?
Seems it's not hard to fix this test, it's necessary just to implement
missing members (at least as stubs) on .NET side in
IgniteConfiguration class.
Is there a Jira issue?
On Fri, Sep 28, 2018 at 2:12 AM Dmitriy
Vladimir, I'm not searching for enemy, and not fighting with you. I'm not
happy about cases when we are hurrying.
We can't fix test, fill ticket details, can't wait for contributions to
finish their tasks. It is not best idea to use experience from commercial
companies in open source. Are there
Let's not revert any commits yet. Can we find out who did the commit and
why he/she is not fixing the test?
D.
On Thu, Sep 27, 2018 at 4:21 PM Vyacheslav Daradur
wrote:
> Hi,
>
> Are you talking about
> 'IgniteConfigurationParityTest#TestIgniteConfiguration'?
>
> Seems it's not hard to fix this
Alexey Kuznetsov created IGNITE-9733:
Summary: Web Console: Add support for "type=number" on InputDialog
Key: IGNITE-9733
URL: https://issues.apache.org/jira/browse/IGNITE-9733
Project: Ignite
Test is going to be fixed in the scope of AI 2.7 [1]. This is not
one-minute fix as there are multiple places where configuration should be
passed, and changes should be covered with tests. I muted the test for now.
[1] https://issues.apache.org/jira/browse/IGNITE-9390
On Fri, Sep 28, 2018 at 2:4
90 matches
Mail list logo
