+1
On Fri, Jun 25, 2021 at 6:34 AM Sergei Ryzhov wrote:
> +1
>
> --
> Best regards,
> Sergei Ryzhov
>
+1 (binding)
On Mon, Jun 28, 2021 at 8:23 PM Вячеслав Коптилин
wrote:
> +1
>
> Thanks,
> S.
>
> пн, 28 июн. 2021 г. в 18:09, Igor Sapego :
>
> > +1
> >
> > Best Regards,
> > Igor
> >
> >
> > On Sat, Jun 26, 2021 at 1:41 AM Nikita Ivanov
> wrote:
> >
> > > +1
> > >
> > > --
> > > Nikita Ivanov
+1
Thanks,
S.
пн, 28 июн. 2021 г. в 18:09, Igor Sapego :
> +1
>
> Best Regards,
> Igor
>
>
> On Sat, Jun 26, 2021 at 1:41 AM Nikita Ivanov wrote:
>
> > +1
> >
> > --
> > Nikita Ivanov
> >
> >
> >
> > On Fri, Jun 25, 2021 at 3:31 PM Valentin Kulichenko <
> > valentin.kuliche...@gmail.com>
+1
Best Regards,
Igor
On Sat, Jun 26, 2021 at 1:41 AM Nikita Ivanov wrote:
> +1
>
> --
> Nikita Ivanov
>
>
>
> On Fri, Jun 25, 2021 at 3:31 PM Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Dear Community,
> >
> > In the last several months, the development of Ignite 3
Seems, we have a silent agreement here :)
We also discussed the proposal with the Ignite QA Meetup participants and
found this contribution useful.
Going to merge tomorrow, if there are no objections.
On Mon, Jun 28, 2021 at 3:21 PM Anton Vinogradov wrote:
> With regard to the request of Ivan
Hello!
Is it WAL (wal/) that is growing or checkpoint space (db/)? If latter, any
specific caches that are growing unbound?
If letter, you can try creating a new cache, moving the relevant data to
this new cache, switch to using it, and then drop the old cache - should
reclaim the space.
Is this why the native disk storage just keeps growing and does not reduce
after we delete from ignite using SQL?
We are up to 80GB on disk now on some instances. We implemented a custom
archiving feature to move older data out of ignite cache to a PostgresSQL
database but when we delete that data
Folks, we already have Ignite release semi-automated at TeamCity.
We able to assembly, publish as RC and check published.
Seems, we must do the same at extensions.
This way we'll check issues like this even before starting the vote.
On Mon, Jun 28, 2021 at 2:14 PM Ilya Kasnacheev
wrote:
>
Hello!
It is being voted on currently, but will need one more round probably.
Regards,
--
Ilya Kasnacheev
пн, 28 июн. 2021 г. в 14:35, Atri Sharma :
> Gentle ping
>
> On Thu, Jun 24, 2021 at 6:36 PM Atri Sharma wrote:
> >
> > Hi All,
> >
> > Can we please publish Spring Sessions Ext
Hello!
I think that number one is the most important one, then maybe it will see
more use and other deficiencies become more apparent, leading to more
tickets and visibility.
Maybe 2. and 3. will even use a different approach when persistence is
implemented.
Regards,
--
Ilya Kasnacheev
пн,
With regard to the request of Ivan Daschinskiy checked that we are able to
release code from the PR.
Looks like everything [1] is fine, ignite-ducketests are not a part of the
zip file.
[1]
Gentle ping
On Thu, Jun 24, 2021 at 6:36 PM Atri Sharma wrote:
>
> Hi All,
>
> Can we please publish Spring Sessions Ext artifacts to the Maven repo?
>
> Atri
--
Regards,
Atri
Apache Concerted
Hello Again!
I have been looking into the aforementioned and here are my follow up thoughts:
1. Support persistence of Lucene indexes.
2. https://issues.apache.org/jira/browse/IGNITE-12401 (Needs fixing of
moving partitions first)
3. Figure out how to return scores from nodes and use them as
Hello!
-1 (binding)
The root element of the source zip file should be
ignite-spring-data-all-ext-1.0.0-src/ directory. No other directories/files
should be at the root of the source zip file.
This is a *blocker* but should be very straightforward to fix.
Regards,
--
Ilya Kasnacheev
пт, 25
Hello.
As one of the authors of PR fully support merge of this module.
Have plans to use it during development of other features.
Guys, please, share your feedback.
Do we need to improve something prior merge?
> 24 июня 2021 г., в 14:41, Denis Magda написал(а):
>
> Anyway, it's much more
15 matches
Mail list logo
