Hi everybody.
Please, review my changes.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Hi Steve, thanks for joining the discussion and sharing your expertise
knowledge! The JDK14 dependency is not a matter of our concern.
Steve, Erick, is there anybody from the Intel engineering who can join the
community and take part in the development? Ignite committers will help
that person(s)
Hi Denis,
Having read through the alternate proposal that would use JEP-352, it all
sounds very plausible and may be a great fit in this case, assuming the
dependency on JDK14 is ok. We are familiar with the persistent ByteBuffer JEP
and think it is a great idea.
Best regards,
Steve
On Oct
Anton, Maxim,
Are we planning to release the views as part of 2.8? Don't see them listed
in the important features section:
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Themostimportantreleasetasks
-
Denis
On Wed, Feb 14, 2018 at 1:49 AM Anton Vinogradov
Igniters,
I came across good introductory slides to Calcite that might be useful to
those of you who are newbies to it as I am :)
https://www.slideshare.net/JordanHalterman/introduction-to-apache-calcite
Added a reference to the IEP.
-
Denis
On Wed, Oct 9, 2019 at 4:03 PM Stamatis Zampetakis
>
> 1. We are going to release Apache Ignite 2.8 with limited support of
>Spark 2.4.4 (known issues are listed here
>https://issues.apache.org/jira/browse/IGNITE-12054)
What does limited support mean? Is it about regressions (something that
worked before but will fail) or capabilities
Folks,
The concept of Apache Bahir is precisely what we need! Saikat, thanks for
doing the research. Why I believe the * idea* fits us well:
- All integrations can be stored in separate Github repositories and
have their dev lifecycles. We've not obliged to couple all the integrations
Amelchev Nikita created IGNITE-12302:
Summary: Test
ZookeeperDiscoveryTopologyChangeAndReconnectTest.testDuplicatedNodeId is broken.
Key: IGNITE-12302
URL: https://issues.apache.org/jira/browse/IGNITE-12302
Alex, Igniters,
This webinar might be relevant as long as we're looking into the
integration with Optane.
-
Denis
Persistent Memory Programming Performance Guidelines
Click here to view this email as a web page.
Nikita,
> Can we include it into a 2.8 release scope?
I think it is possible since the release scope freeze date has not happened yet.
On Thu, 17 Oct 2019 at 17:36, Nikita Amelchev wrote:
>
> Hi, Igniters!
>
> I have implemented the master key change process [1] for TDE as
> described in the
The meeting notes and results of discussion are next:
1. We are going to release Apache Ignite 2.8 with limited support of
Spark 2.4.4 (known issues are listed here
https://issues.apache.org/jira/browse/IGNITE-12054)
2. The AI 2.8 will support both, Spark 2.3 and Spark 2.4.4 with
Hi, Igniters!
I have implemented the master key change process [1] for TDE as
described in the design [2].
I have prepared PR [3] and created the Upsource review branch [4].
Could anyone take a look at my changes?
Can we include it into a 2.8 release scope?
[1]
Aleksey Plekhanov created IGNITE-12301:
--
Summary: Free-lists system view
Key: IGNITE-12301
URL: https://issues.apache.org/jira/browse/IGNITE-12301
Project: Ignite
Issue Type: Sub-task
Hello, Pavel!
Thank you for the feedback!
I've created IEP-38 that describes the Ignite Sandbox [1].
Yes, the issue requires documentation (there is the flag "Docs equired"),
but common practice is to write documentation in the end.
>> 1) Why do you run resource injection through security and
Andrey,
Per you request, I created ticket
https://issues.apache.org/jira/browse/IGNITE-12291 linked to
https://issues.apache.org/jira/projects/IGNITE/issues/IGNITE-12189
Could you please proceed with PR merge ?
BR,
Yuriy Shuliha
ср, 9 жовт. 2019 о 12:52 Andrey Mashenkov пише:
> Hi Yuri,
Denis Garus created IGNITE-12300:
Summary: ComputeJob#cancel executes with wrong SecurityContext
Key: IGNITE-12300
URL: https://issues.apache.org/jira/browse/IGNITE-12300
Project: Ignite
Hello,
Actually I found the answer with the following ticket :
https://issues.apache.org/jira/browse/IGNITE-10801
Seems to be planned for 2.8.0
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hello,
we would like to use new H2 features (especially the OVER keyword)
introduced in 1.4.198. Currently, 2.8.0-SNAPSHOT is relying on 1.4.197. Is
there any plan to upgrade and if not, why? Do you expect any major issue
with that upgrade or the use of the OVER keyword?
Steve
--
Sent from:
Hello!
Historically I support some integrations, so I can final review/merge
integrations commit until someone else steps in.
Regards,
--
Ilya Kasnacheev
чт, 17 окт. 2019 г. в 12:54, Alexey Zinoviev :
> Maybe we could move all our Streaming Integrations there, but what is about
> maintaining
Pavel Kovalenko created IGNITE-12299:
Summary: Store tombstone links into separate BPlus tree to avoid
partition full-scan during tombstones remove
Key: IGNITE-12299
URL:
Pavel Kovalenko created IGNITE-12298:
Summary: Write tombstones on incomplete baseline to get rid of
partition cleanup
Key: IGNITE-12298
URL: https://issues.apache.org/jira/browse/IGNITE-12298
Maybe we could move all our Streaming Integrations there, but what is about
maintaining and committer permissions to the new repositories?
I see the list of the committers and PMC members there
https://bahir.apache.org/community-members/
Could somebody from Ignite community be added to this list
23 matches
Mail list logo
