Hello, Igniters and PMC.
Please, cast your vote.
> 29 апр. 2020 г., в 02:51, Saikat Maitra написал(а):
>
> +1
>
> Yes, we can update the DEVNOTES.txt in the next release.
>
> Regards,
> Saikat
>
>
> On Tue, Apr 28, 2020 at 4:55 AM Maksim Stepachev
> wrote:
>
>> +1
>>
>> вт, 28 апр. 2020
mstekl commented on a change in pull request #10:
URL: https://github.com/apache/ignite-website/pull/10#discussion_r417430944
##
File path: index.html
##
@@ -273,9 +278,9 @@ Applications Acceleration Data Caching
using Ignite as an in-memory data
dmagda commented on pull request #9:
URL: https://github.com/apache/ignite-website/pull/9#issuecomment-621296548
Thanks, Mauricio! Merged.
This is an automated message from the Apache Git Service.
To respond to the message,
Hi Maxim,
Do you have a draft of docs in any form explaining how the feature is
supposed to be used (snapshots creation, restore procedure,
setting/changing snapshots location, etc. - essential operations for such
capabilities)? I can help with the review from the user standpoint and
might advise
Denis,
No, I don't. I'm planning to work on documentation pages right after
we'll finish with the source code changes. I will be very grateful if
you will help with the review of the documentation.
Currently, the approach is very straightforward and simple and I doubt
we can change anything from
dmagda commented on a change in pull request #10:
URL: https://github.com/apache/ignite-website/pull/10#discussion_r417416842
##
File path: index.html
##
@@ -273,9 +278,9 @@ Applications Acceleration Data Caching
using Ignite as an in-memory data
Hi, Ken.
Currently, the Preprocessors are not independent operations yet (to train
OHE separately and re-use the OHE for prediction).
But if you have trained preprocessor (encoder) filled with encoding values
after training process you could re-use it in prediction phase like in
example below.
Folks,
I'm going to merge this issue [1] on the 1-st day of May.
If you still have any questions or PR improvement suggestions, please
let me know.
[1] https://issues.apache.org/jira/browse/IGNITE-11073
On Mon, 27 Apr 2020 at 18:27, Maxim Muzafarov wrote:
>
> Alexey,
>
>
> From my point of
mstekl opened a new pull request #11:
URL: https://github.com/apache/ignite-website/pull/11
Submitting same set of improvements, but removed the usability fix for
descriptive links on homepage.
- Ran a fresh crawl and rebuilt sitemap.xml
- Fixed accessibility issues when using on
Igniters,
I observe several PR notifications for ignite-website on dev list. I
suppose we can redirect them to notificati...@ignite.apache.org as we
do for main ignite repository GitHub notifications.
Does anyone have objections?
How can it be done? As usual with INFRA ticket?
Best regards,
Hi Dmitriy,
Could you please make me an owner of this documentation domain? [1] I need
to grant Nikolay the access but we ran out of seats.
(Igniters, we'll solve this inconvenience once and forever when move our
documentation to GitHub repository).
[1] https://apacheignite-mix.readme.io/docs
Folks,
>
>
> Unfortunately and embarrassingly, we still do not support passing
> INLINE_SIZE to CREATE TABLE, at least in 2.8.0.
I'm confused about this statement. Are we talking about an
issue/regression that slipped into 2.8.0? I do believe the feature worked
before.
-
Denis
On Tue, Apr
Ivan, Nikolay, guys
Sorry if I didn’t put it very clearly. The only caveat I would like to
emphasize is that we must invalidate the results. H2 does this by comparing
table's maxDataModificationId with the databases' current modificationDataId.
We have a H2StatementCache, where Query object
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master
AtomicPartitionCounterStateConsistencyTest.testPartitionConsistencyWithBackupsRestart
Hi Nikolay,
DOCUMENTATION
> https://apacheignite.readme.io/docs/spring-boot-autoconfigure
> https://apacheignite.readme.io/docs/ignite-spring-boot-client-autoconfigure
I unpublished the pages to ensure they are not visible until we release the
extension. In the meantime, we should do the
Maxim,
Ok, let's follow your plan. Ping me once the docs are ready. It's
definitely not a blocker for merging the feature into the master. We can
always adjust the implementation in the master before a public release.
Btw, could you please fill in the "readiness estimated data" column in the
Hi Anton,
Thanks for sharing the plans with details. Could you please do us a favor
and add this item to the roadmap page? I will also help if you link the
item to a JIRA ticket or IEP that includes the details you shared here.
-
Denis
On Tue, Apr 28, 2020 at 12:55 AM Anton Vinogradov wrote:
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master
AtomicPartitionCounterStateConsistencyTest.testPartitionConsistencyWithBackupsRestart
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
Nikolay, the problem is solved and I've arranged access for you. Please
feel free to move the Spring Boot docs to these docs as suggested in the
vote thread:
https://apacheignite-mix.readme.io/docs
-
Denis
On Wed, Apr 29, 2020 at 11:08 AM Denis Magda wrote:
> Hi Dmitriy,
>
> Could you please
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master-nightly
IndexingCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsAfterKillCrdWithPersistence[TRANSACTIONAL]
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 Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master
ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testStopNodeOnSegmentaion
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master
ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testStopNodeOnSegmentaion
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master-nightly
IgnitePdsWithTtlTest.testRebalancingWithTtlExpirable
Hi Ivan,
Please open a ticket for INFRA asking to change the notification alias. I
guess that's my fault - confused aliases when was setting up the repo.
-
Denis
On Wed, Apr 29, 2020 at 10:08 AM Ivan Pavlukhin wrote:
> Igniters,
>
> I observe several PR notifications for ignite-website on
Saikat, please go ahead and merge the changes. They look good to me.
-
Denis
On Mon, Apr 27, 2020 at 4:09 PM Saikat Maitra
wrote:
> Hi Petr,
>
> Yes, I have created an issue to update TC configuration once changes are
> merged.
>
> https://issues.apache.org/jira/browse/IGNITE-12960
>
> Please
Aleksey Plekhanov created IGNITE-12964:
--
Summary: Java thin client: implement cluster group API
Key: IGNITE-12964
URL: https://issues.apache.org/jira/browse/IGNITE-12964
Project: Ignite
28 matches
Mail list logo
