Why not use a combination of Multicast and VM finders? This way we do not
have to make any sacrifices.
D.
On Wed, Jul 18, 2018 at 9:38 PM, Vladimir Ozerov
wrote:
> TcpDiscoveryVmIpFinder can be configured with 127.0.0.1. Example with
> remote nodes will work fine on a single machine. Users
Why can't we use a combination of both, VM and Multicast IP finders?
D.
On Thu, Jul 19, 2018 at 8:28 AM, Stanislav Lukyanov
wrote:
> Yakov,
>
> First, it doesn’t seem likely that many people would run examples on
> several machines. Even if someone would, they’d probably start doing so
> after
Github user DaveWHarvey closed the pull request at:
https://github.com/apache/ignite/pull/4387
---
GitHub user DaveWHarvey opened a pull request:
https://github.com/apache/ignite/pull/4387
Debug Port Fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/percipiomedia/ignite dharvey-ignite-2.5
Alternatively you can review and
I appologize, initially I misundersood proposal. I've concluded that new
doc issue will be created automatically by closing original ticket, - this
can be done by plugin only.
If we just introduce flag or combobox for indicate doc is required, there
is no technical issues, it is defenetely
Ok, if all our doc writers are in the agreement then let's give a couple of
days to our fellow Igniters to share alternate opinions.
Artem, if you don't hear back by Monday then feel free to create an INFRA
ticket.
--
Denis
On Thu, Jul 19, 2018 at 10:43 AM Prachi Garg wrote:
> I totally agree
Hi Alexey,
I can't name myself an ML expert but heard that our ML component is missing
some essential data preprocessing APIs.
Are these pipelines part of our intention to bring in the preprocessing
APIs to Ignite?
--
Denis
On Thu, Jul 19, 2018 at 5:29 AM Alexey Zinoviev
wrote:
> Hi
Dmitriy Pavlov created IGNITE-9036:
--
Summary: Update FasterXML jackson-databind dependency version in
Apache Ignite
Key: IGNITE-9036
URL: https://issues.apache.org/jira/browse/IGNITE-9036
Project:
Dmitriy Pavlov created IGNITE-9035:
--
Summary: Update log4j 2x version in Apache Ignite
Key: IGNITE-9035
URL: https://issues.apache.org/jira/browse/IGNITE-9035
Project: Ignite
Issue Type:
I totally agree with Denis's point -
"Another benefit of having "Docs Required" flag enabled by default, is that
Artem and Prachi can see all such tickets months and weeks before a
release, figure out details from source code contributors and complete the
docs in advance."
On Wed, Jul 18, 2018
Severity: Important
Vendor: The Apache Software Foundation
Versions Affected: Apache Ignite 2.5 and earlier
Impact:
An attacker can execute arbitrary code on Ignite nodes via
GridClientJdkMarshaller deserialization endpoint in the case when Ignite
classpath contains arbitrary vulnerable
Severity: Important
Vendor: The Apache Software Foundation
Versions Affected:
* Apache Ignite 1.0.0-RC3 to 2.5
Impact:
An unauthenticated remote malicious user (or attacker) can issue requests
against Spring Data REST or Spring Data
Description:
Apache Ignite utilizes Spring Data Common
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/4386
IGNITE-8220
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8220-1
Alternatively you can review and apply
Yury Babak created IGNITE-9034:
--
Summary: [ML] Add Estimator API support to TensorFlow cluster on
top of Apache Ignite
Key: IGNITE-9034
URL: https://issues.apache.org/jira/browse/IGNITE-9034
Project:
Yakov,
First, it doesn’t seem likely that many people would run examples on several
machines. Even if someone would, they’d probably start doing so after some
experimentation with a single host – at the moment when they’re already
adjusted enough to check and edit some configs.
Second, I
Github user dgarus closed the pull request at:
https://github.com/apache/ignite/pull/4384
---
Guys, multicast IP finder gives new user an opportunity to run tests on
several machines with zero config changes. And you want to change this
which is not good in my view.
Probably, we need to output warning pointing that user can change multicast
group to avoid undesired discovery and isolate
Hi Dmitriy Pavlov,
MTCGA.Bot seems like useful tool to make analysis and monitoring of our
test base so I also support the idea of publishing its source code.
When it is adopted by more community members they may come up with ideas of
improvements so its sources should be available.
Placing it
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/4071
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4349
---
Hi, Alex!
Could you also help with the ticket [1]? If you have time.
[1] https://issues.apache.org/jira/browse/IGNITE-9020
On Tue, Jul 17, 2018 at 4:50 PM Denis Magda wrote:
>
> Pavel,
>
> Could you chime in please?
>
> --
> Denis
>
> On Tue, Jul 17, 2018 at 6:43 AM Nikita Amelchev
> wrote:
>
Hi Igniters,
I suggest to add and implement by myself sequential pipeline of machine
learning operations including all preprocessing stages like Pipeline object
in Python library scikit-learn (look here
http://scikit-learn.org/stable/modules/generated/sklearn.pipeline.Pipeline.html
for the
Igor Sapego created IGNITE-9033:
---
Summary: .NET: specify expiry policy when creating cache using
thin client
Key: IGNITE-9033
URL: https://issues.apache.org/jira/browse/IGNITE-9033
Project: Ignite
Hi Nikolay,
There was an issue in spring data when we were migrating to spring data
2.0. And if you PR is based on old master branch issue can happen.
Is this PR's base quite fresh?
Sincerely,
Dmitriy Pavlov
чт, 19 июл. 2018 г. в 14:32, Nikolay Izhikov :
> Hello, Igniters.
>
> I faced with TC
Hello, Igniters.
I faced with TC issue for my PR [1]
Seems like some TC misconfiguration.
Locally, all runs OK.
AFAIK, other Igniters also gets this error on TC.
Please, help me with TC configuration.
GitHub user zaleslaw opened a pull request:
https://github.com/apache/ignite/pull/4385
IGNITE-9021
- Fixed tests
- Leave classes used in MLP/DT/another algorithms only
- Fixed code-style for many places
You can merge this pull request into a Git repository by running:
GitHub user dgarus opened a pull request:
https://github.com/apache/ignite/pull/4384
fix 3
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dgarus/ignite ignte-8131_fix_3
Alternatively you can review and apply these changes as
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/4383
IGNITE-9004
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9004
Alternatively you can review and apply these
Github user dgarus closed the pull request at:
https://github.com/apache/ignite/pull/4382
---
Hi Vyacheslav,
For Abbrev plugin I also thought that ASF git repo as primary and
https://github.com/apacheignite mirror would cover all cases.
Thank you for sharing your vision.
Sincerely,
Dmitriy Pavlov
чт, 19 июл. 2018 г. в 9:08, Vyacheslav Daradur :
> I vote for a separate repo for the
Hi Dmitriy,
Yes, I'm going to create INFRA ticket for new ASF supplementary repository
for project, I just want to be absolutely sure, that Community supports my
plan.
Or do you mean I need to create ticket to find out if domain
mtcga.ignite.apache.org is possible to create?
Sincerely,
Dmitriy
GitHub user dgarus opened a pull request:
https://github.com/apache/ignite/pull/4382
IGNITE-8183. fix 3
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dgarus/ignite ignte-8131_fix_3
Alternatively you can review and apply these
Hi Vyacheslav,
Thank you for your feedback.
https://github.com/apacheignite will have mirror from ASF repository, as
docs or main repo have.
Sincerely,
Dmitriy Pavlov
чт, 19 июл. 2018 г. в 8:54, Vyacheslav Daradur :
> I vote for a separate repo for the TC helper project.
>
> IMO TC Helper -
I vote for a separate repo for the Ignite Abbrev Plugin project.
The reason is:
Ignite Abbrev Plugin - build on top of IntelliJ Platform SDK [1] and
can't be easily packaged without it, moreover, it doesn't depend on
Ignite internals (unlike .NET/C++ clients).
One more place where we could place
34 matches
Mail list logo
