Hi Igniters,
I suppose discussion is still at phase 0-Initializing
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
So it is probably no reason to discuss particular blockers. It would make
sense when the process of removal irrelevant tickets starts (phase 1.2) and
till phase 4-
I think, the issue is that Ignite can't recover from
IgniteOutOfMemory, even by removing data.
Shiva, did IgniteOutOfMemory occur for the first time when you did the
DROP TABLE, or before that?
Denis
ср, 25 сент. 2019 г. в 02:30, Denis Magda :
>
> Shiva,
>
> Does this issue still exist? Ignite De
I can help with JDK8 enforcement — just give me the links to target suites when
agreed.
> On 25 Sep 2019, at 01:53, Denis Magda wrote:
>
> Nikolay,
>
> Thanks for the details. How about enforcing JDK 8 for the Spark integration
> in general and run its tests on the VM only? We'll do this unti
Igniters,
It's true that we are still discussing the release dates. But
nevertheless, all the release blockers are important since some of
them may require more than one month to be fixed. Let's discuss today
how we will handle these issues and track Monitoring and ML major
features to get them i
Nikolay,
>> 1. There is no unified approach to adding metrics during development.
> Yes, we have it.
> Just call `MetricRegistry#longMetric` or other method and you got your
> counter.
I talk about code structure, not API.
>> Now the logic is spread throughout the code base and there is now an
Sergey Antonov,
The states ACTIVE, INACTIVE, READ-ONLY look confusing.
Actually read-only cluster is active too.
I would suggest adding new property to Ignite configuration like
setActivationOptions(ActivationOption... options) which should be mutable
in runtime.
For control.sh should be the sam
Hello, Andrey.
> My proposal target is simplification of metrics adding to the code.
> There is no any complexity.
That's great.
Looking forward for your PR.
Please, don't hesitate to request my review for it.
В Ср, 25/09/2019 в 13:23 +0300, Andrey Gura пишет:
> Nikolay,
>
> > > 1. There is no
Stepachev Maksim created IGNITE-12230:
-
Summary: Partition eviction during cache stop / deactivation may
cause errors leading to node failure and storage corruption
Key: IGNITE-12230
URL: https://issues.apache
Hi Maxim,
Thank you for preparing the release page!
Could you please add Require release notes filter? You can find an example
in https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6
Sincerely
Dmitriy Pavlov
ср, 25 сент. 2019 г. в 11:58, Maxim Muzafarov :
> Igniters,
>
>
> I
Andrey Gura created IGNITE-12231:
Summary: RollbackRecord's must be flushed after logging to WAL
Key: IGNITE-12231
URL: https://issues.apache.org/jira/browse/IGNITE-12231
Project: Ignite
Issu
Denis, yes you are right, there is a reason for this.
It's the case when one of a participated node leaves a cluster and loader
send a request to the next node.
Also, the list of participated nodes is limited enough.
Thus, the proposed improvement a) is wrong.
But I think the point b) is still act
Hello Dmitrii Ryabov,
It seems that the following tests fail due to your change
https://issues.apache.org/jira/browse/IGNITE-11094
*IgniteSinkConnectorTest.testSinkPutsWithoutTransformation
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7952366899750322781&b
PetrovMikhail created IGNITE-12232:
--
Summary: NPE while node join processing
Key: IGNITE-12232
URL: https://issues.apache.org/jira/browse/IGNITE-12232
Project: Ignite
Issue Type: Bug
Ilya Suntsov created IGNITE-12233:
-
Summary: Merge benchmarks sql index benchmarks from ignite-2.7 to
master
Key: IGNITE-12233
URL: https://issues.apache.org/jira/browse/IGNITE-12233
Project: Ignite
Bug looks strange. I prepared fix, waiting for TC results.
Hi Dmitrii,
> I prepared fix, waiting for TC results.
Thank you a lot!
Could you please share the JIRA ticket?
Thanks,
S.
ср, 25 сент. 2019 г. в 17:46, Dmitrii Ryabov :
> Bug looks strange. I prepared fix, waiting for TC results.
>
Ivan,
Thank you for interesting question!
Text searches (or full text searches) are mostly human-oriented. And the
point of user's interest is topmost part of response.
Then user can read it, evaluate and use the given records for further
purposes.
Particularly in our case, we use Ignite for ope
Pavel Tupitsyn created IGNITE-12234:
---
Summary: .NET: Fix flaky tests
Key: IGNITE-12234
URL: https://issues.apache.org/jira/browse/IGNITE-12234
Project: Ignite
Issue Type: Improvement
Hi Deepak and welcome!
Sorry for the late response. You sent this message to the user list,
forwarded it to the dev list.
I added you to the Ignite contributors list in JIRA. Feel free to take over
any ticket you like. Do you have any specific interest (SQL, ML, caching,
etc.?
-
Denis
On Sat,
Igniters,
Recently, I've come across a professionally crafted course about Apache
Ignite. It will be interesting for some of you:
https://www.pluralsight.com/courses/apache-ignite-getting-started
Edward, thanks for the course! I've added it to Ignite Doc's menu right
below the book.
-
Denis
I did went trough the course and I asked pluralsight to add more, in the
next course I would like to see ignite installation on aws and spark +
ignite integration.
Real time analytics with spark + ignite.
On Wednesday, September 25, 2019, Denis Magda wrote:
> Igniters,
>
> Recently, I've come a
21 matches
Mail list logo
