Hi Dmitriy,
Thank you, I have updated status to Patch Available.
Regards,
Saikat
On Mon, Jun 25, 2018 at 4:58 AM, Dmitry Pavlov
wrote:
> Hi Saikat,
>
> Could you please set status of
> https://issues.apache.org/jira/browse/IGNITE-3303 to Patch Available, so
> community members can see this
GitHub user ezagumennov opened a pull request:
https://github.com/apache/ignite/pull/4256
IGNITE-8745 Make tcp-disco-worker thread name reflect the node to whiâ¦
You can merge this pull request into a Git repository by running:
$ git pull
Hi, Evaldas!
There no such feature in Web Console yet.
But I think it is worth to implement.
Feel free to create issue in JIRA for this.
But I suppose it is not that trivial and may be not implemented quickly.
On Tue, Jun 26, 2018 at 1:46 AM Evaldas Miliauskas <
e.miliaus...@stacktome.com>
Igniters,
By the results of the recent Ignite meeting at St. Petersburg I've noticed
that some of our users getting stuck with the problem when a cluster is
activated the first time.
At the moment we have only manual options to do it (control.sh, Visor,
etc.), but it's not enough. Manual
GitHub user sk0x50 opened a pull request:
https://github.com/apache/ignite/pull/4255
ignite-8856: Incorrect behavior of BinaryTypeConfiguration in case of using
a wildcard for type names
You can merge this pull request into a Git repository by running:
$ git pull
The Project Management Committee (PMC) for Apache Ignite has invited Joe
Bloggs to become a PMC member and we are pleased to announce that he has
accepted.
Andrey is one of Ignite veterans who participates in the life of the
project daily. Just raw facts:
- ~ 80 contributions of various
GitHub user zaleslaw opened a pull request:
https://github.com/apache/ignite/pull/4254
IGNITE-8741: Added Tutorial
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8741
Alternatively you can review
Done, thanks for your contributions!
--
Denis
On Mon, Jun 25, 2018 at 6:13 AM Иван Федоров wrote:
> Hi, Igniters!
> I'm contributor and I'm not mentioned on contributor page -
> https://ignite.apache.org/community/resources.html
> Could you mention me, please?
> Ivan Fedotov.
>
> 2018-06-25
Folks,
Why don't we read data straight from the persistence layer warming RAM up
in the background? (like we do for SQL and other APIs). If it's a question
of time, then I would suggest us not to hurry up and do it in a right way.
--
Denis
On Mon, Jun 25, 2018 at 6:20 AM Anton Vinogradov
Alexei Scherbakov created IGNITE-8873:
-
Summary: Optimize cache scans with enabled persistence.
Key: IGNITE-8873
URL: https://issues.apache.org/jira/browse/IGNITE-8873
Project: Ignite
Right now I cannot execute a following query in Web Console:
"select count(*) from ReviewCacheRecord where city = ?"
as I get:
[CacheException] class org.apache.ignite.IgniteException: Invalid number of
query parameters. Cannot find 1 parameter.
[IgniteException] Invalid number of query
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4251
---
Anton Kalashnikov created IGNITE-8872:
-
Summary: WAL scanner for crash recovery
Key: IGNITE-8872
URL: https://issues.apache.org/jira/browse/IGNITE-8872
Project: Ignite
Issue Type: Task
Igniters,
If no one objects, then I delete these methods in next refactoring task.
On Fri, Jun 15, 2018 at 6:38 PM Alexey Goncharuk
wrote:
> I have no objections to remove these methods.
>
> --AG
>
> чт, 14 июн. 2018 г. в 17:39, Dmitriy Govorukhin <
> dmitriy.govoruk...@gmail.com>:
>
> >
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4158
---
Nikolay Izhikov created IGNITE-8871:
---
Summary: TDE - Phase-1. Documentation
Key: IGNITE-8871
URL: https://issues.apache.org/jira/browse/IGNITE-8871
Project: Ignite
Issue Type: Sub-task
Nikolay Izhikov created IGNITE-8870:
---
Summary: TDE - Phase-1. Examples
Key: IGNITE-8870
URL: https://issues.apache.org/jira/browse/IGNITE-8870
Project: Ignite
Issue Type: Sub-task
Ivan Daschinskiy created IGNITE-8869:
Summary: PartitionsExchangeOnDiscoveryHistoryOverflowTest
Key: IGNITE-8869
URL: https://issues.apache.org/jira/browse/IGNITE-8869
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4197
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4253
---
GitHub user nizhikov opened a pull request:
https://github.com/apache/ignite/pull/4253
IGNITE-8868: DateFuncSpec added to IgniteDataFrameSuite
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nizhikov/ignite IGNITE-8868
Nikolay Izhikov created IGNITE-8868:
---
Summary: IgniteOptimizationDateFuncSpec not included in
IgniteDataFrameSuite
Key: IGNITE-8868
URL: https://issues.apache.org/jira/browse/IGNITE-8868
Project:
Yury Babak created IGNITE-8867:
--
Summary: Bootstrapping for learning sample
Key: IGNITE-8867
URL: https://issues.apache.org/jira/browse/IGNITE-8867
Project: Ignite
Issue Type: Improvement
Dmitriy,
I consulted with code of *GridDhtPartitionsExchangeFuture*: in its *init*
method only server nodes are added to remaining set, so coordinator will
never wait for clients in order to complete exchange.
So clients are not a problem here.
--
Thanks,
Sergey
On Fri, Jun 22, 2018 at 8:45
Hello, Igniters.
I found that RDD suite doesn't run all scala tests and should be reconfigured.
1. Parameter. TEST_SUITE = "IgniteRDDTestSuite,IgniteDataFrameSuite"
2. Buil Steps. Step3. Additional Maven command line parameters:
"-Pall-java,scala,scala-test".
Petr, can you edit this settings?
+1 to removal in case there is no easy, fast and consistent way to restore
setDataMap on node restart.
I see that we'll gain some performance drop on size() or keys(), but these
methods are rarely used.
пн, 25 июн. 2018 г. в 16:07, Pavel Pereslegin :
> Hello, Igniters.
>
> I tried to implement
Hi, Igniters!
I'm contributor and I'm not mentioned on contributor page -
https://ignite.apache.org/community/resources.html
Could you mention me, please?
Ivan Fedotov.
2018-06-25 13:09 GMT+03:00 Maxim Muzafarov :
> Hello Denis,
>
> Could you, please, add to the list of Ignite contributors:
Hello, Igniters.
I tried to implement IgniteSet data recovery when persistence enabled
[1] using trivial cache scanning, however I cannot find optimal way to
do that because of the following reasons:
- Performing operations on IgniteSet requires completion of data
loading (restoring of
Vladislav Pyatkov created IGNITE-8866:
-
Summary: Need attempt to upload class until node leave or fail
topology by discovery SPI
Key: IGNITE-8866
URL: https://issues.apache.org/jira/browse/IGNITE-8866
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4252
IGNITE-5439 JDBC thin: support query cancel
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5439
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/4251
IGNITE-8840: Random Forest
Implementation of bagging classification logic and random forest
regression/classification based on it
You can merge this pull request into a Git repository by
I’ve modified filter requirements for JDK for Spring build configuration to run
only on u151/u171 of JDK-1.8.0 (it will be 55 agent).
Hope this will be enough.
> On 25 Jun 2018, at 12:54, Nikolay Izhikov wrote:
>
> Hello, Petr.
>
>> I can temporarily assign special rule for agent JDK and
Hello Denis,
Could you, please, add to the list of Ignite contributors: Prabhat Ranjan
(rprabhat)
https://ignite.apache.org/community/resources.html
He has got his first commit into Ignite.
https://issues.apache.org/jira/browse/IGNITE-8436
вт, 29 мая 2018 г. в 20:19, Denis Magda :
> Hello
Hi Saikat,
Could you please set status of
https://issues.apache.org/jira/browse/IGNITE-3303 to Patch Available, so
community members can see this issue in their filters?
Sincerely,
Dmitriy Pavlov
вс, 24 июн. 2018 г. в 4:30, Saikat Maitra :
> Hi,
>
> I have updated the PR for IGNITE-3303. I
Hello, Petr.
> I can temporarily assign special rule for agent JDK and fix theirs Java later.
I'm not Team City guru, so I'm don't understand your proposal :)
All I need is make sure Core and Spring suites for my branch [1] are executed
with latest jdk.
Can you make it for me?
[1]
Crossposting to dev.
Hi Igniters,
Is it possible to change graceful shutdown way as described below?
Do we have any plans for this?
-- Forwarded message -
From: Dave Harvey
Date: Fri, Jun 22, 2018 at 11:26 PM
Subject: Running Node removal from baseline
To:
The
Nokolay,
Agents prior publicagent10 has u77 inded, while publicagent10-17 has already
u171.
I can temporarily assign special rule for agent JDK and fix theirs Java later.
> On 25 Jun 2018, at 10:33, Nikolay Izhikov wrote:
>
> Hello, Igniters.
>
> I'm trying to run tests for TDE branch.
>
Hello, Igniters.
I'm trying to run tests for TDE branch.
It seems I'm facing with known JDK bug [1]
Here is log from Team City [2].
As I can see current Team City jdk is 1.8.0_77-b03
Issue JDK-8149411 fixed in 8u102.
Can we upgrade JDK on Team City?
[1]
Hi Pavel,
Thank you a lot for the response.
Best Regards,
Roman
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
39 matches
Mail list logo
