Alexey, thanks, that's the source code I named as Payments Fraud Detection:
https://github.com/dmagda/ignite-ml-examples/blob/master/logistic-regression-example/src/main/java/org/apache/ignite/example/ClientNode.java
-
Denis
On Wed, Sep 18, 2019 at 2:27 AM Alexey Zinoviev
wrote:
> Cool
Hi Nikolay,
Because in the discussion below, there is a list describing that ROWNUM
is not applicable to Ignite, and I want to know why.
在 2019/9/18 下午11:14, Nikolay Izhikov 写道:
Hello, liyuj.
Please, clarify.
Do you want to contribute this to Ignite?
What explanation do you expect?
В Ср,
Igniters,
2.8 release cycle can last for many months due to a number of issues and
regressions we need to address. It can easily slip to the next year,
especially considering the holiday season. An alternate solution can be a
series of Ignite 2.7.x releases that are becoming more hardened with
Nikolay, thanks for participating.
I have supplemented the design and clarify these moments. [1]
[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652381
ср, 18 сент. 2019 г. в 16:48, Nikolay Izhikov :
>
> Hello, Nikita.
>
> Thanks for starting this discussion.
>
> 1. We
Rohit Joshi created IGNITE-12198:
Summary: GridDiscoveryManager uses hardcoded failure handler
Key: IGNITE-12198
URL: https://issues.apache.org/jira/browse/IGNITE-12198
Project: Ignite
Issue
Denis,
It's not fundamental, but quite complex. In postgres, for example, this is
not maintained automatically and store compaction is performed using the
full vacuum command, which acquires exclusive table lock, so no concurrent
activities on the table are possible.
The solution which Anton
Andrey Gura created IGNITE-12197:
Summary: Incorrect way for getting value of persistent enabled in
CacheGroupMetricsImpl
Key: IGNITE-12197
URL: https://issues.apache.org/jira/browse/IGNITE-12197
Igniters,
Currently, from my perspective, the Apache Ignite has a very raw
rebalance process metrics. Moreover, the most interesting metrics are
related to the Cache, not a CacheGroup and require enabling cache
statistics which can affect node performance.
Some of the metrics are not working as
Maxim Muzafarov created IGNITE-12196:
Summary: [Phase-4] Deprecate old rebalancing cache metrics
Key: IGNITE-12196
URL: https://issues.apache.org/jira/browse/IGNITE-12196
Project: Ignite
Igniters,
I am following the release process procedure [1] and currently on docs
update step. I can login to the admin panel, but I can only see the main
Ignite docs project. Who can add me to the remaining projects (C#/.NET,
C++, SQL, Integrations*, Ignite for Spark, Tools) or perhaps clone the
Maxim Muzafarov created IGNITE-12195:
Summary: [Phase-3] Rebalance HitRate metrics
Key: IGNITE-12195
URL: https://issues.apache.org/jira/browse/IGNITE-12195
Project: Ignite
Issue Type:
Maxim Muzafarov created IGNITE-12194:
Summary: [Phase-2] Calculate expected rebalancing cache group keys
Key: IGNITE-12194
URL: https://issues.apache.org/jira/browse/IGNITE-12194
Project: Ignite
Maxim Muzafarov created IGNITE-12193:
Summary: [Phase-1] Rebalancing cache group keys metric counters
Key: IGNITE-12193
URL: https://issues.apache.org/jira/browse/IGNITE-12193
Project: Ignite
Hello, liyuj.
Please, clarify.
Do you want to contribute this to Ignite?
What explanation do you expect?
В Ср, 18/09/2019 в 22:46 +0800, liyuj пишет:
> Hi,
>
> Can anyone explain how difficult it is to implement ROWNUM?
>
> This is a very common requirement.
>
> 在 2018/1/23 下午4:05, Serge
Hi,
Can anyone explain how difficult it is to implement ROWNUM?
This is a very common requirement.
在 2018/1/23 下午4:05, Serge Puchnin 写道:
yes, the Cust function is supporting both Ignite and H2.
I've updated the documentation for next system functions:
CASEWHEN Function, CAST, CONVERT, TABLE
Hello, Nikita.
Thanks for starting this discussion.
1. We should add prerequisites for "master key rotation process" in design.
Seems, it should be, "New master key available to EncryptionSPI for each server
node".
2. Please, use code formatting in wiki. It's make reading easier.
3. Please,
Stephen Darlington created IGNITE-12192:
---
Summary: visorcmd hangs if you ^D to quit
Key: IGNITE-12192
URL: https://issues.apache.org/jira/browse/IGNITE-12192
Project: Ignite
Issue
One more point to discuss: Wouldn't it be better to have enabled system
views by default?
To enable views admin must restart the node, sometimes it's an issue.
Views cost almost nothing in terms of performance until they are explicitly
requested, so is their a reason to disable views by default?
Hi, Igniters.
I'm going to implement the ability to rotate the master encryption key
(TDE Phase 2). [1]
Master key rotation required in case of it compromising or at the end
of crypto period(key validity period). I prepared the design. [2]
In briefly, master keys will be identified by String
Nikolay Izhikov created IGNITE-12191:
Summary: Add support of system view and metric to Visor
Key: IGNITE-12191
URL: https://issues.apache.org/jira/browse/IGNITE-12191
Project: Ignite
Yuriy Shuliha created IGNITE-12190:
---
Summary: Throw an exception for enabled text queries on persistent
caches
Key: IGNITE-12190
URL: https://issues.apache.org/jira/browse/IGNITE-12190
Project:
Yuriy Shuliha created IGNITE-12189:
---
Summary: Implement correct limit for TextQuery
Key: IGNITE-12189
URL: https://issues.apache.org/jira/browse/IGNITE-12189
Project: Ignite
Issue Type:
Aleksey Plekhanov created IGNITE-12188:
--
Summary: Metric CacheGroupMetrics.IndexBuildCountPartitionsLeft
doesn't work correctly if there is more then one cache in cache group
Key: IGNITE-12188
URL:
Start of December for 2.8 sounds good.
В Ср, 18/09/2019 в 13:38 +0300, Alexey Zinoviev пишет:
> Sounds good for me, I will be ready to release ML module till 1 December
> (end of September is not appropriate for ML module due to known issues and
> bugs)
> If the whole Ignite could be released to
Sounds good for me, I will be ready to release ML module till 1 December
(end of September is not appropriate for ML module due to known issues and
bugs)
If the whole Ignite could be released to this date I will be happy in
another case I suggest the minor release by the formula mentioned above.
Alexey,
>> Can you describe the complete protocol changes first
The current goal is to find a better way.
I had at least 5 scenarios discarded because of finding corner cases
(Thanks to Alexey Scherbakov, Aleksei Plekhanov and Nikita Amelchev).
That's why I explained what we able to improve and
Nikolay Izhikov created IGNITE-12187:
Summary: [IEP-35] Move GridMetricManager and dependent classes to
org.apache.ignite.internal.managers
Key: IGNITE-12187
URL:
Folks,
Agree, we should start a discussion about releasing Apache Ignite 2.8
version right after 2.7.6 will be announced.
Am I missing something?
On Wed, 18 Sep 2019 at 12:33, Nikolay Izhikov wrote:
>
> > of 2.7 release
>
> It's 2.8, of course. Sorry, for typo.
>
>
> В Ср, 18/09/2019 в 12:36
Amelchev Nikita created IGNITE-12186:
Summary: TDE - Phase-2. Master key rotation.
Key: IGNITE-12186
URL: https://issues.apache.org/jira/browse/IGNITE-12186
Project: Ignite
Issue Type:
> of 2.7 release
It's 2.8, of course. Sorry, for typo.
В Ср, 18/09/2019 в 12:36 +0300, Nikolay Izhikov пишет:
> Hello, Alexey
>
> > we have no chance to
> > release the whole master branch
>
> Why do you think so?
> From my point of view, we should start discussion of 2.7 release, shortly(end
Hello, Alexey
> we have no chance to
> release the whole master branch
Why do you think so?
From my point of view, we should start discussion of 2.7 release, shortly(end
of September of similar)
В Ср, 18/09/2019 в 12:04 +0300, Alexey Zinoviev пишет:
> Dear Igniters, for the whole year I'm
I've started the discussion here
http://apache-ignite-developers.2346864.n4.nabble.com/Proposed-Release-2-7-7-2-7-6-ML-extra-fixed-bugs-td43537.html
пт, 13 сент. 2019 г. в 22:12, Alexey Zinoviev :
> The reason was that the last year there is no significant releases of
> Ignite between 2.7 and
Cool presentation, thank you for evangelism for ML module
Could you share the link on the code from demo: Payments Fraud Detection?
вт, 17 сент. 2019 г. в 02:25, Denis Magda :
> Hey Ignite dev and user communities,
>
> Those of you who are passionate about ML and Ignite ML in particular, we
>
Dear Igniters, for the whole year I'm waiting for the next release of
Apache Ignite with number 2.8 or 3.0. As I understand we have no chance to
release the whole master branch, but we have cool changes in ML component
that were not released since 2.7 (Nomember 2018).
I'm ready to become a
Aleksandr Brazhnikov created IGNITE-12185:
-
Summary: [IEP-35] Add metrics - how many indexes are left to
rebuild
Key: IGNITE-12185
URL: https://issues.apache.org/jira/browse/IGNITE-12185
Aleksandr Brazhnikov created IGNITE-12184:
-
Summary: [IEP-35] Add metrics - status rebild indexes
Key: IGNITE-12184
URL: https://issues.apache.org/jira/browse/IGNITE-12184
Project: Ignite
Aleksandr Brazhnikov created IGNITE-12183:
-
Summary: [IEP-35] Add metrics rebalancing
Key: IGNITE-12183
URL: https://issues.apache.org/jira/browse/IGNITE-12183
Project: Ignite
Issue
Anton,
I looked through the presentation and the ticket but did not find any new
protocol description that you are going to implement. Can you describe the
complete protocol changes first (to save time for both you and during the
later review)?
Some questions that I have in mind:
* It looks
Stephen Darlington created IGNITE-12182:
---
Summary: ExecutorService is inconsistent with Compute and
Services, runs on clients
Key: IGNITE-12182
URL: https://issues.apache.org/jira/browse/IGNITE-12182
Igniters,
Recently we had a discussion devoted to the non-blocking PME.
We agreed that the most important case is a blocking on node failure and it
can be splitted to:
1) Affected partition’s operations latency will be increased by node
failure detection duration.
So, some operations may be
Denis,
I like the idea of throwing an exception for enabled text queries on
persistent caches.
Also I'm fine with proposed limit for unsorted searches.
Yury, please proceed with ticket creation.
вт, 17 сент. 2019 г., 22:06 Denis Magda :
> Igniters,
>
> I see nothing wrong with Yury's proposal
41 matches
Mail list logo
