Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New test failure in master
CacheAbstractTest.TestCacheConfigurationExpiryPolicy
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4531
---
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/4599
IGNITE-9353: Removed "Known issue, possible deadlock in case of low pâ¦
â¦riority cache rebalancing delayed" comment from
GridCacheRebalancingSyncSelfTest#getConfiguration.
You can merge this
Github user shroman closed the pull request at:
https://github.com/apache/ignite/pull/4598
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4597
---
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/4598
IGNITE-9353: Removed "Known issue, possible deadlock in case of low pâ¦
â¦riority cache rebalancing delayed" comment from
GridCacheRebalancingSyncSelfTest#getConfiguration.
You can merge this
Roman Shtykh created IGNITE-9353:
Summary: Remove "Known issue, possible deadlock in case of low
priority cache rebalancing delayed" comment from
GridCacheRebalancingSyncSelfTest#getConfiguration
Key: IGNITE-9353
Alexey Kuznetsov created IGNITE-9352:
Summary: Web Console: Investigate how correctly use
package-lock.json
Key: IGNITE-9352
URL: https://issues.apache.org/jira/browse/IGNITE-9352
Project: Ignite
GitHub user akuznetsov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4597
IGNITE-9350 Added checks for empty data in web sockets events.
You can merge this pull request into a Git repository by running:
$ git pull
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*Recently contributed test failed in master
TransactionIntegrityWithPrimaryIndexCorruptionTest.testPrimaryIndexCorruptionDuringCommitOnPrimaryNode3
GitHub user kukushal opened a pull request:
https://github.com/apache/ignite/pull/4596
Spark Streaming with Ignite: MD POC
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-spark-streaming
Dmitriy, Alex, thanks for clarification, this is that i already mention in
ticket.
I think this approach correct.
Try to provide PR soon.
thanks!
>
>--- Forwarded message ---
>From: "Alex Plehanov" < plehanov.a...@gmail.com >
>To: dev@ignite.apache.org
>Cc: arzamas...@mail.ru
Github user alamar closed the pull request at:
https://github.com/apache/ignite/pull/4594
---
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/4595
IGNITE-9351 Log restore partition state start and finish events with â¦
â¦elapsed time
You can merge this pull request into a Git repository by running:
$ git pull
Dmitriy Pavlov created IGNITE-9351:
--
Summary: Log restore partition state start and finish events with
elapsed time
Key: IGNITE-9351
URL: https://issues.apache.org/jira/browse/IGNITE-9351
Project:
Vladimir,
This ticket [1] can be closed, right? All the thing clients in Ignite 2.6
go with authentication capabilities.
However, not sure what's the status of the other task [2].
[1] https://issues.apache.org/jira/browse/IGNITE-6941
[2] https://issues.apache.org/jira/browse/IGNITE-6856
On
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4594
Ignite gg 14002
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-14002
Alternatively you can review and apply
Nikolay,
Whatever we decide on would be right :) Basically, we need to answer this
question: does the catalog exist in scope of a single IgniteSparkSession
(and therefore single IgniteContext and single Ignite instance)? In other
words, in case of a rare use case when a single Spark application
Hi Dmitry,
That's a BSD-3-Clause license if to believe this statement
"SPDX-License-Identifier: BSD-3-Clause":
https://github.com/pmem/llpl/blob/master/LICENSE
This license can be used with ASF software:
https://www.apache.org/legal/resolved.html#category-a
--
Denis
On Wed, Aug 22, 2018 at
Alexey Kuznetsov created IGNITE-9350:
Summary: Web Console backend should not fail if null received via
web sockets
Key: IGNITE-9350
URL: https://issues.apache.org/jira/browse/IGNITE-9350
Github user alamar closed the pull request at:
https://github.com/apache/ignite/pull/4529
---
GitHub user xtern opened a pull request:
https://github.com/apache/ignite/pull/4593
IGNITE-9305
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-9305
Alternatively you can review and apply these changes as
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4592
IGNITE-9054 Avoid using OptimizedMarshaller with initial ScanQuery.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4578
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4432
---
Oleg Ignatenko created IGNITE-9348:
--
Summary: ML examples improvements, follow-up to IGNITE-9297
Key: IGNITE-9348
URL: https://issues.apache.org/jira/browse/IGNITE-9348
Project: Ignite
Vladimir Ozerov created IGNITE-9347:
---
Summary: Attempt to start a dynamic cache with invalid
configuration leads to exchange worker death
Key: IGNITE-9347
URL: https://issues.apache.org/jira/browse/IGNITE-9347
Hi Denis,
Could you please double check if we can refer to any library licensed to
Intel. Can we develop code only version of this support (without shipping
it in release)?
https://github.com/apache/ignite/pull/4381 is quite huge change, including
128 files changed, patch review will require
Issue [1] created.
[1] https://issues.apache.org/jira/browse/IGNITE-9346
пн, 20 авг. 2018 г. в 17:27, Denis Magda :
> Yes, let’s just remove md5. Will you create the ticket and handle this for
> 2.7?
>
> Denis
>
> On Monday, August 20, 2018, Anton Vinogradov wrote:
>
> > Denis,
> >
> >
Anton Vinogradov created IGNITE-9346:
Summary: md5 should be removed from release
Key: IGNITE-9346
URL: https://issues.apache.org/jira/browse/IGNITE-9346
Project: Ignite
Issue Type: Task
Hello Maxim,
Thank you for your work. I will review your changes within the next several
days.
2018-08-22 11:12 GMT+03:00 Maxim Muzafarov :
> Pavel,
>
> Thank you for so detailed introduction into the root of the problem of
> ticket IGNITE-7196.
> As you mentioned before, we can divide this
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4527
---
Hello, Igor.
Thanks, for an answer.
I think we should start with a simple step by step how-to: "How to build
current sources?".
Actually, I don't know how I can help you with this task?
Seems, only you have the knowledge of this process.
At this step, no source changes required.
I propose to
Nikolay,
You are right, it should be much easier.
Unfortunately, there are very few C++ developers in community.
I'm planning on fix all these, but I'm always lack time. I'd appreciate
a lot and provide any help if anyone could help me with those tasks.
Best Regards,
Igor
On Wed, Aug 22, 2018
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4579
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4550
---
Vladimir Ozerov created IGNITE-9345:
---
Summary: Document custom SQL schemas
Key: IGNITE-9345
URL: https://issues.apache.org/jira/browse/IGNITE-9345
Project: Ignite
Issue Type: Task
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/4586
---
Hi Igniters,
It seems it is a flaky test. We need to improve flakiness detection in the
Bot. Please join separate discussion started by Dmitrii Ryabov.
Sincerely,
Dmitriy Pavlov
ср, 22 авг. 2018 г. в 3:22, :
> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/4580
---
Hi,
I think we should provide an article "Ignite.C++ development" in the
project's wiki.
Such article as "Ignite.NET Development" [1] helped me to prepare the
environment step by step.
[1] https://cwiki.apache.org/confluence/display/IGNITE/Ignite.NET+Development
On Wed, Aug 22, 2018 at 12:06
Hello, Igniters.
While working on IGNITE-6055 [1] I need to do some fixes in ODBC.
I find out that setup of local CPP development environment is a very hard task:
1. Linux -
- We use a very old version of boost library.
Modern Linux distribution uses the new one.
Igniters,
I've checked this failure. Can't reproduce it locally.
It seems mentioned commits are not related to this test. The test has been
a long
flaky and we just got an unlucky day to catch fail 3 times in a row.
I think, we should fix it as an ordinary MTCGA way. Issue created - [1]
[1]
Maxim Muzafarov created IGNITE-9344:
---
Summary: Flaky test `testClientReconnectClusterActivated` detected
Key: IGNITE-9344
URL: https://issues.apache.org/jira/browse/IGNITE-9344
Project: Ignite
Hello, Valentin.
> I believe we should get rid of this logic and use Ignite schema name as
> database name in Spark's catalog.
When I develop Ignite integration with Spark Data Frame I use following
abstraction described by Vladimir Ozerov:
"1) Let's consider Ignite cluster as a single
Hi Val, yes that's correct. I'd be happy to make the change to have the
database reference the schema if Nikolay agrees. (I'll first need to do a
bit of research into how to obtain the list of all available schemata...)
Thanks,
Stuart.
On Tue, Aug 21, 2018 at 9:43 PM, Valentin Kulichenko <
GitHub user macrergate opened a pull request:
https://github.com/apache/ignite/pull/4591
Ignite gg 13195 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-gg-13195-2.5.1-master
Pavel,
Thank you for so detailed introduction into the root of the problem of
ticket IGNITE-7196.
As you mentioned before, we can divide this ticket into two sub-tasks. So,
I will
file new issue for `Logical consistency recovery`. I think it's more
convenient way
for reviewing and merging each of
48 matches
Mail list logo
