Denis A. Magda created IGNITE-13935:
---
Summary: Update Ignite docker image description
Key: IGNITE-13935
URL: https://issues.apache.org/jira/browse/IGNITE-13935
Project: Ignite
Issue Type:
Hi Mike,
Thanks for providing your feedback. Please see my comments below.
I would also encourage you to go through the IEP-54 [1] - it has a lot of
detail on the topic.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach
-Val
On Mon, Dec 28, 2020 at 11:22
Congrats, community!
Yaroslav, thanks for driving the release. Look forward to collaborating
with all of you in 2021. Let's rock and happy New Year!
-
Denis
On Tue, Dec 29, 2020 at 4:17 AM Yaroslav Molochkov
wrote:
> The Apache Ignite Community is pleased to announce the release of
> Apache
Valentin Kulichenko created IGNITE-13934:
Summary: Some of the source files are missing license headers
Key: IGNITE-13934
URL: https://issues.apache.org/jira/browse/IGNITE-13934
Project:
Valentin Kulichenko created IGNITE-13933:
Summary: Add an ability to customize documentation source repo
Key: IGNITE-13933
URL: https://issues.apache.org/jira/browse/IGNITE-13933
Project:
Thanks, Maksim,
Considering that most of the contributors will be on holidays through Jan
10th, it's highly unlikely that all documentation tickets will be ready by
Jan 18th (the vote date).
Anyway, Nikita confirmed that he'll be actively working on the tickets
starting Jan 11th. As for me,
Hi, Igniters!
ASF welcomes all types of contributions, including responses to user
questions and promotion of projects. And, the GriGain DelRel team knows
that people spend a lot of their private time on such activities. Our code
and documentation contributors are recognized by being promoted to
Nikita Safonov created IGNITE-13932:
---
Summary: Extend Ignite thread pools documentation
Key: IGNITE-13932
URL: https://issues.apache.org/jira/browse/IGNITE-13932
Project: Ignite
Issue
Great news!
Congrats to all the community with one more release!
Yaroslav and Maxim thanks for driving it!
> 29 дек. 2020 г., в 15:17, Yaroslav Molochkov
> написал(а):
>
> The Apache Ignite Community is pleased to announce the release of
> Apache Ignite 2.9.1.
>
> Apache Ignite [1] is a
The Apache Ignite Community is pleased to announce the release of
Apache Ignite 2.9.1.
Apache Ignite [1] is a memory-centric distributed database, caching
and processing platform for transactional, analytical, and streaming
workloads delivering in-memory speeds at petabyte scale.
This release
Nikolay Izhikov created IGNITE-13931:
Summary: .NET: Service can't assign correct type to passed array
parameters (.Net -> .Net call)
Key: IGNITE-13931
URL: https://issues.apache.org/jira/browse/IGNITE-13931
Sure, I will do it right away, thanks a lot!
On Tue, Dec 29, 2020 at 2:02 PM Maxim Muzafarov wrote:
> Folks,
>
> I've finished (with some help) all the release steps.
> I think we are ready for the announcement.
>
>
> Yaroslav,
>
> Can you check that everything is ok?
>
> On Mon, 28 Dec 2020 at
Maxim Muzafarov created IGNITE-13930:
Summary: Update pom depencencies to 2.11.0-SNAPSHOT version
Key: IGNITE-13930
URL: https://issues.apache.org/jira/browse/IGNITE-13930
Project: Ignite
Michael, thanks for feedback.
1. However, there is no decision approved by the community, but I heard a
lot about it would be nice to have one table\schema per cache.
Actually, we already have CacheGroup, a very useful feature that allows us
to share memory region/persistence files between caches
Folks,
The branch `ignite-2.10` for the release has been created.
The list of issues related to 2.10 release [1]. If I excluded your
issue you are working on from the release feel free to set the
`fixVersion` back.
[1] https://s.apache.org/qa6kk
On Tue, 29 Dec 2020 at 11:43, Maxim Muzafarov
Sergey Uttsel created IGNITE-13929:
--
Summary: Don't print sensitive information in logs by default
Key: IGNITE-13929
URL: https://issues.apache.org/jira/browse/IGNITE-13929
Project: Ignite
Folks,
I've finished (with some help) all the release steps.
I think we are ready for the announcement.
Yaroslav,
Can you check that everything is ok?
On Mon, 28 Dec 2020 at 13:47, Ilya Kasnacheev wrote:
>
> Hello!
>
> Please make sure that it gets pushed before the long holidays. I don't
>
Ilya,
Thanks for feedback.
1. It is a Nested Builder pattern [1]. With a nested builder user will have
a single entry point to build a schema.
When you have a number of builders and one builder need a result of some
another builder, users can be confused and waste a time while looking for
proper
Semyon Danilov created IGNITE-13928:
---
Summary: Index defragmentation: only one index defragmented
Key: IGNITE-13928
URL: https://issues.apache.org/jira/browse/IGNITE-13928
Project: Ignite
Hello!
Is there a way to define schema via ignitectl utility and its
hierarchical properties? How would it look like?
Regards,
--
Ilya Kasnacheev
пн, 21 дек. 2020 г. в 17:40, Andrey Mashenkov :
> Hi, Igniters.
>
> We all know that the current QueryEntity API is not convenient and needs to
>
Hello, Andrei!
I have read this thread and PR. The builder idea and API looks good. But I
have some questions.
1.
In SchemaTableBuilder:
When I use a builder in chain style, I expect in every step the same result
type. And as I see this idea is implemented anywhere except pk(), where you
return
Folks,
1.
I've prepared the list of unhandled important documentation issues for
the 2.10 release, please check the wiki page link [1]. Note, that some
of the important (from my point of view) documentation issues even not
created.
2.
Here is the list of resolved issues which seems to be
22 matches
Mail list logo
