Ivan Pavlukhin created IGNITE-12574:
---
Summary: Fix failing IoStatisticsBasicIndexSelfTest
Key: IGNITE-12574
URL: https://issues.apache.org/jira/browse/IGNITE-12574
Project: Ignite
Issue
We could not because of multiple hibernate modules, what is considered from the
javadoc's point as warning, that always fails test.
> On 24 Jan 2020, at 11:02, Ivan Pavlukhin wrote:
>
> Maxim,
>
> I suppose we can try to enable "javadoc" profile for a corresponding
> job. Are there any
Stanilovsky Evgeny created IGNITE-12577:
---
Summary: High persistence load can trigger erroneous assert: "Page
was pin when we resolve abs pointer, it can not be evicted".
Key: IGNITE-12577
URL:
Maxim,
I suppose we can try to enable "javadoc" profile for a corresponding
job. Are there any objections to do so?
пн, 20 янв. 2020 г. в 13:25, Ivan Pavlukhin :
>
> Maxim,
>
> From the first glance it seems that "javadoc" profile was really
> missed. Are there any other problems except
Alexey Goncharuk created IGNITE-12575:
-
Summary: Document @IgniteExperimental annotation
Key: IGNITE-12575
URL: https://issues.apache.org/jira/browse/IGNITE-12575
Project: Ignite
Issue
Ivan Bessonov created IGNITE-12576:
--
Summary: [IEP-35] TCP communication metrics use node ID instead of
consistent ID
Key: IGNITE-12576
URL: https://issues.apache.org/jira/browse/IGNITE-12576
Ivan,
I believe that the removal of the thread group is harmless. Let's check
with the rest of the community, and if there is no objections, remove it.
пт, 24 янв. 2020 г. в 11:13, Ivan Pavlukhin :
> Alex,
>
> > We can either remove it (not sure if this is a breaking public API
> change?)
> >
Thanks to all for the review, the annotation has been added, also created
an additional ticket for documentation.
вт, 21 янв. 2020 г. в 16:23, Alexey Goncharuk :
> Pavel, Igor,
>
> Can you add similar annotations/attributes to platforms?
>
> вт, 21 янв. 2020 г. в 16:01, Alexey Goncharuk >:
>
>>
Alex,
> We can either remove it (not sure if this is a breaking public API change?)
> or create a separate thread group per Ignite instance and pass it to the
> constructor of IgniteThread (quite a lot of refactoring).
Recently there were a discussion about "magic stuff" in codebase. And
it
Hi,
As you might know IndexingSpi is a candidate for removal in Ignite
3.0. But perhaps we can drop it earlier (e.g. in 2.9). Are there any
strong reasons to keep it? And is there an evidence that it works fine
in current versions? Does someone use it?
My personal concern here are complexities
Aleksey Plekhanov created IGNITE-12578:
--
Summary: CAS cache operations (replace(K, V, V), remove(K, V))
don't work with array data type
Key: IGNITE-12578
URL:
> My point - that your contribution that took a long time, already, can’t be an
> argument to postpone creation of the API in the current release.
Argument is not about time. But about API which is known will be changed.
Second argument: why we should add this experimental API to the
already
PetrovMikhail created IGNITE-12579:
--
Summary: SQL INSERT operation hangs with security enabled.
Key: IGNITE-12579
URL: https://issues.apache.org/jira/browse/IGNITE-12579
Project: Ignite
Alexey Scherbakov created IGNITE-12580:
--
Summary: NPE in GridMetricManager
Key: IGNITE-12580
URL: https://issues.apache.org/jira/browse/IGNITE-12580
Project: Ignite
Issue Type: Bug
Folks,
This test began to constantly fail in the master branch [2] and the
2.8 [1] also. It seems it's related to the [3] issue (IGNITE-12531:
Cluster is unable to change BLT on 2.8 if storage was initially
created on 2.7 or less) which have been recently fixed and
cherry-picked to 2.8.
Can you
We've discussed thin client compute protocol with Pavel Tupitsyn and Igor
Sapego and come to the conclusion that approach with two-way requests
should be used: client generates taskId and send a request to the server to
execute a task. The server responds that the request has been accepted.
After
Folks,
It's true that my simple assumption (to include Javadoc profile) will
not work by reasons mentioned by Petr. I've tested it under a new
experimental suite [1] which I've created earlier. We will always have
such warnings due to we have multiple modules with the same package
declarations
Vladimir,
Welcome to Apache Ignite Community!
I added a contributor role to your Jira account. Now you can assign
tickets to yourself. Please get familiar with the contribution process
[1].
By the way,
> I've just joined a team with the commiters.
Could you tell us what team did you join?
Great, Thanks!
On Fri, Jan 24, 2020 at 1:14 PM Alexey Goncharuk
wrote:
> Thanks to all for the review, the annotation has been added, also created
> an additional ticket for documentation.
>
> вт, 21 янв. 2020 г. в 16:23, Alexey Goncharuk >:
>
> > Pavel, Igor,
> >
> > Can you add similar
Hello everyone!
My name is Vladimir. I'd like to become new contributor of Apache Ignite as
a developer. I've just joined a team with the commiters. I've been working
as Java developer more than 10 years with a bunch of various frameworks and
solutions. Now I'm interrested in modern open source
Actually, I got stuck with a question what do modules like
ignite-hibernate mean from a javadoc standpoint. It seems that modules
sharing same packages and classes cannot be aggregated into valid
javadoc bundle. And actually this problem should be solved as well
(modularization?). But I suppose
Folks,
I've cherry-picked these issues [1] [2] to the 2.8 release branch.
[1] https://issues.apache.org/jira/browse/IGNITE-12540
Update versions of vulnerable dependencies
[2] https://issues.apache.org/jira/browse/IGNITE-12486
Truncation of archived WAL segments doesn't work
On Thu, 23 Jan
Petr,
Thank you for that detail! Unfortunately I do not know how to fix it easily.
Also I found that even without "javadoc" profile we miss some javadoc
problems. I believe that it can be fixed by updating post-build
javadoc checking condition. See below what problems do we miss (and
there are a
Hello Emmanouil,
It would be great if we have at least basic integration tests in real AWS
environment. Even though they may require more work to keep them green (I
mean here AWS quotas and additional configuration/reconfiguration efforts)
it worth it because these tests can also be useful as an
Taras,
I believe we should have the same mechanism but different
set of flags.
Alexey,
The idea is to add new flag when you make changes instead of
increment protocol version. This way client maintainer can introduce
the same change (probably fix) in they client without the necessity to
Hi Luis,
Presently, the community is on the route of Ignite simplification. We're
trying to define Ignite core that has minimal dependencies with 3rd party
libraries. That also led to the modularization initiative [1] with the
first results in the form of Ignite Extensions repository where we're
cant open second screenshot I mean cant expand , a simple example to read
and write with spark would be nice using thrift jdbc etc ...
connecting Ignite from outside ec2 with spark.
Hi!
We are trying to deploy an ignite cluster(s) into kubernetes and found some
issues.
Sample deployed topology into kubernetes (we need each ignite server cluster
has different discovery port)
Ignite Server(s) cluster to store main data (discoPort 49500)
\
Client App with 2 ignite
Sergey,
Thanks for a compact and clear article. I especially enjoyed the part that
explains how to connect from a local laptop to an already running Ignite
cluster on AWS. Looking forward to more content from you!
-
Denis
On Wed, Jan 22, 2020 at 11:35 PM Sergey Chugunov
wrote:
> Hello
29 matches
Mail list logo
