Pavel Konstantinov created IGNITE-9568:
--
Summary: Web console: fields are not visible under Firefox
Key: IGNITE-9568
URL: https://issues.apache.org/jira/browse/IGNITE-9568
Project: Ignite
Ilya Borisov created IGNITE-9569:
Summary: Web console: use $inject for DI instead of arrays
Key: IGNITE-9569
URL: https://issues.apache.org/jira/browse/IGNITE-9569
Project: Ignite
Issue Type
Vladimir Ozerov created IGNITE-9570:
---
Summary: Fix failures in CacheMvccSelectForUpdateQueryAbstractTest
Key: IGNITE-9570
URL: https://issues.apache.org/jira/browse/IGNITE-9570
Project: Ignite
Pavel Konstantinov created IGNITE-9571:
--
Summary: Web console: update Project Structure UI to a new style
Key: IGNITE-9571
URL: https://issues.apache.org/jira/browse/IGNITE-9571
Project: Ignite
Igniters,
I need your help with the review of this patch. In general, it will help to
reduce PME duration. I've moved binary
memory recovery at the moment of node startup as we've discussed it with
Pavel previously this topic.
Changes are relatively small (+299 −95) and they are ready. I've left
GitHub user Max-Pudov opened a pull request:
https://github.com/apache/ignite/pull/4742
Ignite 2.4.8 p4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.8-p4
Alternatively you can review and appl
Ilya Borisov created IGNITE-9572:
Summary: Web console: broken in Edge 17
Key: IGNITE-9572
URL: https://issues.apache.org/jira/browse/IGNITE-9572
Project: Ignite
Issue Type: Bug
R
GitHub user pavlukhin opened a pull request:
https://github.com/apache/ignite/pull/4743
IGNITE-8149: fix for CI
Fail DataStreamProcessorMvccSeflTest referring to IGNITE-9451 and mention
same ticket in GridDhtPartitionsStateValidator.
You can merge this pull request into a Git repos
Ilya Kasnacheev created IGNITE-9573:
---
Summary: ZookeeperDiscoverySpiSaslFailedAuthTest fails after added
to suite
Key: IGNITE-9573
URL: https://issues.apache.org/jira/browse/IGNITE-9573
Project: Ign
GitHub user dgarus opened a pull request:
https://github.com/apache/ignite/pull/4744
IGNITE-6454 reproducer fast finish
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dgarus/ignite IGNITE-6454_fix
Alternatively you can review a
Github user pavlukhin closed the pull request at:
https://github.com/apache/ignite/pull/4743
---
GitHub user pavlukhin opened a pull request:
https://github.com/apache/ignite/pull/4745
IGNITE-9411: mvcc timeouts
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9411
Alternatively you can review a
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/4746
Ignite 1.9.14
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.9.14
Alternatively you can review and apply t
SomeFire opened a new pull request #8: Trigger build bugfix
URL: https://github.com/apache/ignite-teamcity-bot/pull/8
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub a
Aleksey Zinoviev created IGNITE-9574:
Summary: Document Gradient boosting
Key: IGNITE-9574
URL: https://issues.apache.org/jira/browse/IGNITE-9574
Project: Ignite
Issue Type: Task
Aleksey Zinoviev created IGNITE-9575:
Summary: Document Binary Logistic Regression
Key: IGNITE-9575
URL: https://issues.apache.org/jira/browse/IGNITE-9575
Project: Ignite
Issue Type: Task
Aleksey Zinoviev created IGNITE-9576:
Summary: Document Multi-Class Logistic Regression
Key: IGNITE-9576
URL: https://issues.apache.org/jira/browse/IGNITE-9576
Project: Ignite
Issue Type:
Aleksey Zinoviev created IGNITE-9577:
Summary: Document Preprocessing
Key: IGNITE-9577
URL: https://issues.apache.org/jira/browse/IGNITE-9577
Project: Ignite
Issue Type: Task
Co
Aleksey Zinoviev created IGNITE-9578:
Summary: Document K-fold cross validation of models
Key: IGNITE-9578
URL: https://issues.apache.org/jira/browse/IGNITE-9578
Project: Ignite
Issue Typ
Aleksey Zinoviev created IGNITE-9579:
Summary: Document Random Forest
Key: IGNITE-9579
URL: https://issues.apache.org/jira/browse/IGNITE-9579
Project: Ignite
Issue Type: Task
Co
Igniters,
As most of you know, Ignite has a concept of AffinityTopologyVersion, which
is associated with nodes that are currently present in topology and a
global cluster state (active/inactive, baseline topology, started caches).
Modification of either of them involves process called Partition Ma
Alexey Platonov created IGNITE-9580:
---
Summary: Fix exit code 137 in Query 1 Suite
Key: IGNITE-9580
URL: https://issues.apache.org/jira/browse/IGNITE-9580
Project: Ignite
Issue Type: Bug
Aleksey Zinoviev created IGNITE-9581:
Summary: Document ANN algorithm based on ACD concept
Key: IGNITE-9581
URL: https://issues.apache.org/jira/browse/IGNITE-9581
Project: Ignite
Issue Ty
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/4747
IGNITE-9580: Added setMaxSize for ignite configuration in test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
Aleksey Zinoviev created IGNITE-9582:
Summary: Document Model Updating
Key: IGNITE-9582
URL: https://issues.apache.org/jira/browse/IGNITE-9582
Project: Ignite
Issue Type: Task
C
Hello,
I propose the following.
*Development*
1. Define *IDependencyResolver* in *Apache.Ignite.Core* under
*DependencyInjection* folder that contains at least 2 methods:
*T Resolve(object arguments = null);*
*object Resolve(Type type, object arguments = null);*
2. Create *InjectResolvableAttr
Hi, Dmitriy,
Can you give me rights to stop my builds on TeamCity? Working on the TCH, I
run a lot of builds, and I don't like to ask other people to stop builds
too often.
2018-09-10 23:53 GMT+03:00 Dmitrii Ryabov :
> Hi, Dmitriy,
>
> I made PRs in my fork for test purposes. Real PRs were made
asfgit closed pull request #8: Trigger build bugfix
URL: https://github.com/apache/ignite-teamcity-bot/pull/8
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:
As this is a foreign pull request (from
Dmitry,
Thanks for your example! The approach looks similar to "problematic" on
used in jdk described in [1]. Fortunately, in our case buffer is quite
limited. On the other hand we always should be cautious because Ignite code
frequently is running on user threads (e.g. it is typical for SQL).
[1
11.09.2018 14:46, Igor Sapego пишет:
1) I meant auto-generated doc, this page: [1]. By the way,
many methods do not have any description as well.
Updated - introduction sentences placed on the main page of the
autogenerated API spec.
All public methods have description, except setters for
Igor Sapego created IGNITE-9583:
---
Summary: PHP thin: php directory should be included in binary
release
Key: IGNITE-9583
URL: https://issues.apache.org/jira/browse/IGNITE-9583
Project: Ignite
Good.
5) I've filed a separate ticket, so it can be taken by a someone,
who is familiar with our build system: [1]
[1] - https://issues.apache.org/jira/browse/IGNITE-9465
Best Regards,
Igor
On Thu, Sep 13, 2018 at 5:07 PM Alexey Kosenchuk <
alexey.kosenc...@nobitlost.com> wrote:
> 11.09.2
Alexey Goncharuk created IGNITE-9584:
Summary: .NET DataStorageMetricsTest is flaky in master
Key: IGNITE-9584
URL: https://issues.apache.org/jira/browse/IGNITE-9584
Project: Ignite
Issue
GitHub user macrergate opened a pull request:
https://github.com/apache/ignite/pull/4748
Ignite 2.5.1 master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-master
Alternatively you can review
Oleg Ignatenko created IGNITE-9585:
--
Summary: Error message sometimes refers nonexisting log file when
remote node fails to start
Key: IGNITE-9585
URL: https://issues.apache.org/jira/browse/IGNITE-9585
Hello, Stuart.
Do you need any assistance with this task from me or other community member?
В Вт, 04/09/2018 в 19:03 +0300, Nikolay Izhikov пишет:
> Hello, Stuart.
>
> Sorry for the silence.
>
> I was swamped the last couple of days.
>
> I think you can go forward and implement suggested solut
GitHub user zaleslaw opened a pull request:
https://github.com/apache/ignite/pull/4749
IGNITE-9022: Changed class label output in SVM
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9022
Alternative
Ilya Kasnacheev created IGNITE-9586:
---
Summary: Treat 172.17.0.1 as localhost address and only use it as
last resort
Key: IGNITE-9586
URL: https://issues.apache.org/jira/browse/IGNITE-9586
Project: I
Looks good to me in general.
But we should add IDependencyResolver {get;set} to IgniteConfiguration
class instead of changing IIgnite interface.
We need the resolver at startup before IIgnite instance is created, to
resolve user-defined cache stores and so on.
And we should make sure to add tests
Aleksey Zinoviev created IGNITE-9587:
Summary: [ML] Umbrella ticket: Handle different labels in training
data and handle unknown labels in test or updated training data correctly
Key: IGNITE-9587
URL: https://
Hi, Igniters
Welcome to the discussion about labels handling during ML training.
The problem is that all algorithms of binary classification are ready to
handle the datasets marked with 0/1 labels and predict 0/1 labels without
especial mapping.
Also the algorithms don't handle situation with un
Hi Dmitriy,
Sure, I agree with extra permissions assignment. Done.
Could you please check if you can manage your builds now?
Sincerely,
Dmitriy Pavlov
чт, 13 сент. 2018 г. в 16:05, Dmitrii Ryabov :
> Hi, Dmitriy,
>
> Can you give me rights to stop my builds on TeamCity? Working on the TCH, I
>
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/4750
IGNITE-8770: OutOfMemory in Queries1 suite in master branch on TC
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ign
Yep, it's working. Thank you.
2018-09-13 19:09 GMT+03:00 Dmitriy Pavlov :
> Hi Dmitriy,
>
> Sure, I agree with extra permissions assignment. Done.
>
> Could you please check if you can manage your builds now?
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 13 сент. 2018 г. в 16:05, Dmitrii Ryabov :
>
> >
Ryabov Dmitrii created IGNITE-9588:
--
Summary: Separate page for JIRA, GitHub actions
Key: IGNITE-9588
URL: https://issues.apache.org/jira/browse/IGNITE-9588
Project: Ignite
Issue Type: Sub-t
Amelchev Nikita created IGNITE-9589:
---
Summary: GridTcpCommunicationSpiConfigSelfTest.testLocalPortRange
is flaky in master
Key: IGNITE-9589
URL: https://issues.apache.org/jira/browse/IGNITE-9589
Pro
GitHub user NSAmelchev opened a pull request:
https://github.com/apache/ignite/pull/4751
IGNITE-9589
For IGNITE-9589 GridTcpCommunicationSpiConfigSelfTest.testLocalPortRange
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NSAmelch
Ok, now everything's running.
API looks good to me. I have a single question about example code:
What these comments are for - [1]?
[1] -
https://github.com/nobitlost/ignite/blob/ignite-7782/modules/platforms/python/examples/create_binary.py#L95
Best Regards,
Igor
On Thu, Sep 13, 2018 at 12:52
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4752
IGNITE-8006 added parallel start of caches.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8006
Alternatively y
zzzadruga opened a new pull request #9: IGNITE-9541 Add the comparison for two
general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9
This is an automated messag
GitHub user oignatenko opened a pull request:
https://github.com/apache/ignite/pull/4753
IGNITE-9585 Error message sometimes refers nonexisting log file when remote
node fails to start
You can merge this pull request into a Git repository by running:
$ git pull https://github
GitHub user ignitetcbot opened a pull request:
https://github.com/apache/ignite/pull/4754
Ignite 9349
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/ignite ignite-9349
Alternatively you can review and apply these changes
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4700
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4754
---
Hello, Igniters!
We've improved tests analysis in the TeamCity Helper.
Now, when you view PR analysis, you can see a table with possible blockers
- failed tests and suites, that most likely appeared in the pull request.
Ilya,
Thanks for the detailed explanation. Everything you suggested makes sense.
Needless to say, PME effect on the grid should be minimized. Let's start
with the simpler and less risky changes first.
D.
On Thu, Sep 13, 2018 at 5:58 AM Ilya Lantukh wrote:
> Igniters,
>
> As most of you know, I
Hello, Dmitrii.
Can you give a link to detailed description of this feature?
Actually, I wonder if someone except bit developers know how to use it
чт, 13 сент. 2018 г., 22:46 Dmitrii Ryabov :
> Hello, Igniters!
>
> We've improved tests analysis in the TeamCity Helper.
>
> Now, when you view PR
Roman Kondakov created IGNITE-9590:
--
Summary: MVCC: Cleanup old rows in the vacuum thread.
Key: IGNITE-9590
URL: https://issues.apache.org/jira/browse/IGNITE-9590
Project: Ignite
Issue Type:
Roman Kondakov created IGNITE-9591:
--
Summary: MVCC: Do small write operations under the read lock.
Key: IGNITE-9591
URL: https://issues.apache.org/jira/browse/IGNITE-9591
Project: Ignite
Iss
Roman Kondakov created IGNITE-9592:
--
Summary: MVCC: Use linked lists to store multiple versions.
Key: IGNITE-9592
URL: https://issues.apache.org/jira/browse/IGNITE-9592
Project: Ignite
Issue
Igor,
The commented code (lines 95-96) gives an error if executed. The error
is stated just below, in lines 98-100. It is explained here:
https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/examples.html#create
I found out by trial and error that a cache, created with SQL DD
Nikolay Izhikov created IGNITE-9593:
---
Summary: Spart Optimization fails to optimize statements
Key: IGNITE-9593
URL: https://issues.apache.org/jira/browse/IGNITE-9593
Project: Ignite
Issue
Hello, Denis.
I've created a tests for Ignite codebase and attached it to the ticket [1].
[1] https://issues.apache.org/jira/browse/IGNITE-9593
В Вт, 11/09/2018 в 13:34 +0300, Nikolay Izhikov пишет:
> Hello, Denis.
>
> Thanks for providing reproducers for bugs!
>
> I taked a look at your proje
Alexey Kuznetsov created IGNITE-9594:
Summary: Regression in release build for ignite-zookeeper module
Key: IGNITE-9594
URL: https://issues.apache.org/jira/browse/IGNITE-9594
Project: Ignite
Ilya Borisov created IGNITE-9595:
Summary: Web console: invisible checkbox is visible inqueries
Key: IGNITE-9595
URL: https://issues.apache.org/jira/browse/IGNITE-9595
Project: Ignite
Issue T
Ilya Borisov created IGNITE-9596:
Summary: Web console: invisible checkbox is visible
Key: IGNITE-9596
URL: https://issues.apache.org/jira/browse/IGNITE-9596
Project: Ignite
Issue Type: Bug
Hi Folks,
There is no description of this feature yet. But I think we should come
back to the idea of running a webinar.
Please share your vision. If Igniters will attend I send an invitation to
the beginning of next week.
I hope in the nearest time we will have a few more features to speak abou
Hello, Dmitriy.
Webinar is a great idea, let's have it.
В Пт, 14/09/2018 в 09:39 +0300, Dmitriy Pavlov пишет:
> Hi Folks,
>
> There is no description of this feature yet. But I think we should come
> back to the idea of running a webinar.
>
> Please share your vision. If Igniters will attend I
68 matches
Mail list logo
