Denis, Emmanouil,
Sure, I'll take a look at the code shortly.
--
Thank you,
Sergey.
On Mon, Jan 27, 2020 at 8:59 PM Denis Magda wrote:
> I support the idea of triggering such tests on demand. We can create a wiki
> page with instructions on how to run the tests. Unless there is a more
> elegan
Stepan Pilschikov created IGNITE-12587:
--
Summary: ML examples failed on start
Key: IGNITE-12587
URL: https://issues.apache.org/jira/browse/IGNITE-12587
Project: Ignite
Issue Type: Bug
Stepan Pilschikov created IGNITE-12588:
--
Summary: Failed to run MLeap or Spark examples
Key: IGNITE-12588
URL: https://issues.apache.org/jira/browse/IGNITE-12588
Project: Ignite
Issue Ty
Dmitrii,
I'm not a security expert, but I have a concern about the usage
of common purpose mechanism for authentication purposes.
I mean any other component seem to be able to get this data which
should be private. Looks like a dangerous hack to me, to be honest.
Maybe we should create and use s
PetrovMikhail created IGNITE-12589:
--
Summary: Remote thin client operations are not authorized
correctly.
Key: IGNITE-12589
URL: https://issues.apache.org/jira/browse/IGNITE-12589
Project: Ignite
Hello!
We already have several "security contexts" and we even have some code
which tries to clear sensitive data from it.
However, it is no good for authenticating nodes anyway, since discovery
message have to travel via ring, so all server nodes will have access to
sensitive information.
Regar
Ilya,
The fact that we have some security holes does not sound to me
like a good reason to create a new one.
Best Regards,
Igor
On Tue, Jan 28, 2020 at 12:22 PM Ilya Kasnacheev
wrote:
> Hello!
>
> We already have several "security contexts" and we even have some code
> which tries to clear se
Thanks guys,
It's a pleasure to be a part of this great community
Best Regards,
Igor
On Mon, Jan 27, 2020 at 9:26 PM Denis Magda wrote:
> Igor, thanks for being an invaluable member of the community all this time!
> Congrats!
>
> -
> Denis
>
>
> On Sun, Jan 26, 2020 at 9:58 PM Ivan Pavlukhin
Taras Ledkov created IGNITE-12590:
-
Summary: MERGE INTO query is failing on Ignite client node
Key: IGNITE-12590
URL: https://issues.apache.org/jira/browse/IGNITE-12590
Project: Ignite
Issue
Igor,
I see nothing criminal in attribute visibility to internal Ignite
components. It could be a hole if attributes were available through public
API.
вт, 28 янв. 2020 г., 13:07 Igor Sapego :
> Ilya,
>
> The fact that we have some security holes does not sound to me
> like a good reason to cre
Ivan Pavlukhin created IGNITE-12591:
---
Summary: Scan query scans invalid partitions on unstable topology
Key: IGNITE-12591
URL: https://issues.apache.org/jira/browse/IGNITE-12591
Project: Ignite
Igor Seliverstov created IGNITE-12592:
-
Summary: Calcite integration. Query load balancing.
Key: IGNITE-12592
URL: https://issues.apache.org/jira/browse/IGNITE-12592
Project: Ignite
Issue
Anton Kalashnikov created IGNITE-12593:
--
Summary: Corruption of B+Tree caused by byte array values and TTL
Key: IGNITE-12593
URL: https://issues.apache.org/jira/browse/IGNITE-12593
Project: Ignite
Anton Kalashnikov created IGNITE-12594:
--
Summary: Deadlock between GridCacheDataStore#purgeExpiredInternal
and GridNearTxLocal#enlistWriteEntry
Key: IGNITE-12594
URL: https://issues.apache.org/jira/browse/IGN
Merged to master [1]
Igniters, I want to release both modules I added.
Do we have documentation, how it should be done for ignite-extensions?
[1]
https://github.com/apache/ignite-extensions/commit/575ec510e4d48b1e0c2ec7e4cf8d596e7de82f70
пн, 27 янв. 2020 г. в 13:06, Nikolay Izhikov :
> Hello, A
Vladimir Steshin created IGNITE-12595:
-
Summary: Parametrization of GridCacheSetAbstractSelfTest
Key: IGNITE-12595
URL: https://issues.apache.org/jira/browse/IGNITE-12595
Project: Ignite
Vladimir Steshin created IGNITE-12596:
-
Summary: Parametrization of IgniteCacheAbstractExecutionContextTest
Key: IGNITE-12596
URL: https://issues.apache.org/jira/browse/IGNITE-12596
Project: Ignite
Vladimir Steshin created IGNITE-12597:
-
Summary: IgniteTxStoreExceptionAbstractSelfTest
Key: IGNITE-12597
URL: https://issues.apache.org/jira/browse/IGNITE-12597
Project: Ignite
Issue Typ
Hi,
I failed to find where CacheConfiguration.DefaultLockTimeout property
is used. Does anyone know how is it used? If it is not used I suppose
we can mark this property deprecated.
Please share your thoughts!
--
Best regards,
Ivan Pavlukhin
Looks like i found problem root cause, first run completed on TC, hope it would
be ok with other builds.
>
>
>--- Forwarded message ---
>From: "Ivan Pavlukhin" < vololo...@gmail.com >
>To: dev < dev@ignite.apache.org >
>Cc:
>Subject: Re: Cache 6 suite is broken
>Date: Fri, 20 Dec 2019
Folks,
Let me share my humble opinion over this thread. The first priority
here is making Ignite better and taking the next step with releasing
Ignite's 2.8 version for our users (we've already done a great job
with metrics).
According to this point of view and from the user perspective I'd like
Maxim.
I’m +1 to do it.
> 1. Let's keep @deprecated annotation to notify users earlier.
> 2. Let's fix javadoc comments for this annotation (remove internal
> references).
We also have a consensus to add IgniteExperimental annotation to the new
metrics API.
> 28 янв. 2020 г., в 19:05, Maxim M
Andrey,
I've looked through those changes [1] and now they look good to me.
Let's do the following:
1. Get a fresh TC.Bot visa
2. Merge these changes to the master branch.
3. After that and 3-day stabilization cherry-pick to 2.8
Should we wait for benchmarks? I think at this release stage any
ad
Maxim.
> Should we wait for benchmarks?
After review, these changes looks much safer for me - no additional metrics
added.
I performed benchmarking for initial refactoring of
`TcpCommunicationMetricsListener` on the new Metric API.
It seems, there is no need for benchmarking anymore.
> 28 янв
Igniters,
Here is the list of actual release BLOCKER issues:
[1] Keep in mind unfinished discussion about internal classes
IGNITE-12456 [2] Cluster Data Store grid gets Corrupted for Load test
*[Unassigned]* OPEN
IGNITE-12398 Apache Ignite Cluster(Amazon S3 Based Discovery) Nodes getting
down [E
Igniters,
I've just published an article that describes one of the reasons for why an
Ignite cluster can underperform. It's reviewed how a selection of proper
Ignite APIs can put less pressure on the network and proliferate the
performance:
https://www.gridgain.com/resources/blog/why-my-in-memory-
--
-
With best regards, Sergey Chernolyas
My jiraId is schernolyas
--
-
With best regards, Sergey Chernolyas
Hi Nikolay,
Here is the release process docs for Ignite [1]
We do not have docs specific to Ignite Extensions, we will need to create
docs for Ignite Extensions.
Please find discussion on release process below [2]
Regards,
Saikat
[1] https://cwiki.apache.org/confluence/display/IGNITE/Release+
> A protocol for one feature can change from release to release.
I think about it in a following way. Imagine that we reworked somehow
affinity awareness and changes are needed on a protocol level. From a
features point of view old feature is AffinityAwarenessV1 and new one
is AffinityAwarenessV2.
Hi Sergey,
Welcome to the Apache Ignite Community.
Do you need some assistance? Or might be you have something to tell
the Community. Do not hesitate to write back.
I see that your Jira account was already added to the contributors
list. You can find some contribution guidelines at
https://cwiki
Manu,
Looks like it is currently impossible to use custom discovery port
with TcpDiscoveryKubernetesIpFinder. This limitation is covered in
code of a method
org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder#parseAddresses
Feel free to create a Jira issue for a
Vladimir,
Do no hesitate to write back if you need any assistance, e.g. troubles
with code or a code review.
пн, 27 янв. 2020 г. в 13:28, Vladimir Steshin :
>
> Ok. Forgot to explain the ticket. I'm going to bring some refactoring to
> the test, replace inheritance with parametrization. Many test
Ivan, thanks. It's ok. I'm waiting for the test results, researching the
code, doing next simple ticket.
ср, 29 янв. 2020 г., 10:38 Ivan Pavlukhin :
> Vladimir,
>
> Do no hesitate to write back if you need any assistance, e.g. troubles
> with code or a code review.
>
> пн, 27 янв. 2020 г. в 13:28
Hi Ivan!
Thank you very much for your email. Yes, I need some assistance because I
am new at contribution to the the project. But .. I did some PR to Ignite
project two years ago. In spice of it, I need a assistance.
I have created ticket https://issues.apache.org/jira/browse/IGNITE-12582 .
My cu
Hi igniters!
I have created new channel "#ignite-spring-framework" for discussion about
integration with Spring Framework.
--
-
With best regards, Sergey Chernolyas
36 matches
Mail list logo
