Anton,
Could you please review the page about Read Rapair?
https://apacheignite.readme.io/docs/read-repair
-Artem
On 05.03.2020 12:20, Artem Budnikov wrote:
OK, I'll recreate it.
Nikolay, please let me know when you are finished with the Metrics and
system views documentation. I'm done with the list of docs we
identified in this thread and want to publish v. 2.8.
-Artem
On 05.03.2020 11:55, Maxim Muzafarov wrote:
Artem,
I've created that. It is not public and can be safely removed since
it's a full copy of 2.7.6 (at that moment)
On Thu, 5 Mar 2020 at 11:53, Artem Budnikov
<a.budnikov.ign...@gmail.com> wrote:
Guys,
I see that there is already version 2.8 for Ignite docs on readme.io.
Who created it and when? I've changed some pages under 2.7.6 version
without knowing that there is a newer version.
-Artem
On 05.03.2020 11:45, Artem Budnikov wrote:
I'm confused. Igor, could you please double check?
-Artem
On 05.03.2020 04:15, Ivan Pavlukhin wrote:
That's right, only C++ and .NET clients have partition awareness
Are your sure? Was not the feature implemented for java thin client
in [1]?
[1] https://issues.apache.org/jira/browse/IGNITE-11898
Best regards,
Ivan Pavlukhin
ср, 4 мар. 2020 г. в 18:18, Denis Magda <dma...@apache.org>:
Maxim,
Yes, it's preferable to have metrics pages fully completed even
though the
feature is an experimental state. We want to encourage to try it out
and
switch to the new APIs eventually. Without technical instructions
available
our users will have a hard time checking the new capabilities.
Nikolay, thanks a lot!
-
Denis
On Wed, Mar 4, 2020 at 8:52 AM Nikolay Izhikov <nizhi...@apache.org
wrote:
I think yes.
I will prepare documentation shortly.
4 марта 2020 г., в 17:50, Maxim Muzafarov <mmu...@apache.org>
написал(а):
Folks,
Do we need a fully complete public documentation for metrics
marked
with @ExperimentalFeature? The API can significantly be changed.
On Wed, 4 Mar 2020 at 17:10, Artem Budnikov
<a.budnikov.ign...@gmail.com>
wrote:
The only feature that is left is "WAL page compression"
The three other features are limitations that were present in
Ignite
2.7 and now they are removed. Since they were never mentioned
in the
docs, there is nothing to do.
-Artem
On 04.03.2020 17:02, Denis Magda wrote:
I'll work on the following items today and tomorrow:
- JDBC: Support for query cancellation
- JDBC: Support for query timeout
- suspend/resume for pessimistic transactions
- WAL page compression
Artem, are these the only tickets left apart from the metrics &
monitoring? @Nikolay
Izhikov <nizhi...@apache.org> how soon will you be able to
finish the
metrics documentation pages?
-
Denis
On Wed, Mar 4, 2020 at 2:55 AM Artem Budnikov
<abudni...@gridgain.com>
wrote:
Hi everyone,
I have created the docs for the following items so far:
- Default Ignite work dir location
https://apacheignite.readme.io/docs/getting-started-28#section-setting-up-work-directory
- Baseline auto-adjust feature
https://apacheignite.readme.io/docs/baseline-topology-28#section-baseline-topology-autoadjustment
- Cluster (de)activation events documentation
https://apacheignite.readme.io/docs/baseline-topology-28#section-cluster-activationdeactivation-events
- Remove SqlQuery documentation
done
- Partition awareness for thin clients
https://apacheignite-net.readme.io/docs/thin-client-28#section-partition-awareness
https://apacheignite-cpp.readme.io/docs/thin-client-28#section-partition-awareness
- Transactions support in java thin client
https://apacheignite.readme.io/docs/key-value-28#section-client-transactions
- KILL QUERY command
https://dash.readme.io/project/apacheignite-sql/v2.7.6/docs/kill-query
- Move rebalance configuration properties to the
IgniteConfiguration level
https://apacheignite.readme.io/docs/data-rebalancing-28#section-configuration
- Renamed IGNITE schema to SYS
done
I'll work on the following items today and tomorrow:
- JDBC: Support for query cancellation
- JDBC: Support for query timeout
- suspend/resume for pessimistic transactions
- WAL page compression
Nikolay,
How is your progress with the Metrics and System Views
documentation?
Artem Budnikov
Technical Writergridgain.com
On 03.03.2020 19:06, Maxim Muzafarov wrote:
Folks,
This is in the `Ignite Core` section, so I think mostly
related to
java functionality and thin client protocol extension [1].
Sorry for
not being too accurate with this statement
.
The same change is mentioned for C++ and .NET sections of the
release
notes (but not for other thin clients).
[1] https://issues.apache.org/jira/browse/IGNITE-11898
On Tue, 3 Mar 2020 at 17:33, Igor Sapego <isap...@apache.org>
<
isap...@apache.org> wrote:
That's right, only C++ and .NET clients have partition
awareness
Best Regards,
Igor
On Tue, Mar 3, 2020 at 5:02 PM Artem Budnikov
<abudni...@gridgain.com>
<abudni...@gridgain.com>
wrote:
Hi everyone,
Looks like the following line from the Ignite 2.8 release notes
is a
bit
of an overstatement and should be removed:
Added support best effort affinity for thin clients (partition
awareness)
Java thin client does not support partition awareness.
Nodejs and
python
thin clients from the distribution package do not have signs of
this
feature as well.
Igor,
Could you please confirm or deny this?
-Artem
Artem Budnikov
Technical Writergridgain.com
On 03.03.2020 01:47, Denis Magda wrote:
Hi Alexey,
Thanks for updating the documentation. The update process is
cumbersome as
of now. What will happen is that we will be replacing the
content of
the
current pages (pre 2.8 pages) with the content from the 2.8
versions.
Once
the text is copied manually, a 2.8 version of the page will be
deleted. I
would advise Artem to do that this time and update the wiki
page with
more
details:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document
Also, why should we release this page?
https://dash.readme.io/project/apacheignite/v2.7.6/docs/genetic-algorithms
-
Denis
On Sun, Mar 1, 2020 at 7:59 AM Alexey Zinoviev <
zaleslaw....@gmail.com> <zaleslaw....@gmail.com>
wrote:
Hi, Igniters, I've finished the ML documentation.
I have the issue that, for example I've created a new version
of page
with
postfix -2.8 and the page name contains this postfix.
How are we going to replace the URL? Or we will replace the
content
from
initial page?
For example, I've created the new version of pagehttps://
dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees
and
moved it under new pagehttps://
dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees-28
How it will be processed to obtain the decision-trees url for
the new
page?
In all case the full list of removed/replaced pages for ML is
next:
In the release 2.8, please remove the pages
1.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/genetic-algorithms
2.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/svm-multi-class-classification
3. DeepLearning block with 3 pages
4.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/model-cross-validation
Next pages were replaced with postfix 2.8 and grouped under new
pages
1.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/machine-learning
2.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/preprocessing
3.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/ols-multiple-linear-regression
4.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/k-means-clustering
5.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/multilayer-perceptron
6.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/knn-classification
7.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/knn-regression
8.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/svm-binary-classification
9.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/logistic-regression
10.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/random-forest
11.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/gradient-boosting
12.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/model-updating
13.
https://dash.readme.io/project/apacheignite/v2.7.6/docs/ann-approximate-nearest-neighbor
ср, 26 февр. 2020 г. в 03:32, Denis Magda <dma...@apache.org>
<
dma...@apache.org>:
Hi Prasad,
This is odd behavior and before changing the docs I would try
to get
to
the
bottom. Let me join the user list conversation.
-
Denis
On Tue, Feb 25, 2020 at 3:46 AM Prasad Bhalerao <
prasadbhalerao1...@gmail.com> wrote:
Hi,
Can we have this behavior documented? This will help user to
design
their
caches appropriately.
*For Replicated Cache:*
Reference mail thread:
http://apache-ignite-users.70518.x6.nabble.com/Read-through-not-working-as-expected-in-case-of-Replicated-cache-td29990.html
read through for replicated cache would work where there is
either:
- writeThrough enabled and all changes do through it.
- database contents do not change for already read keys.
Thanks,
Prasad
On Mon, Feb 24, 2020 at 7:31 PM Alexey Zinoviev <
zaleslaw....@gmail.com>
wrote:
Please, could you post in this thread a few examples of the
documentation
tickets in JIRA for the current release, to create them
correctly?
пн, 24 февр. 2020 г. в 14:53, Alexey Zinoviev <
zaleslaw....@gmail.com
:
Ok, will make ticket, no problemo
вс, 23 февр. 2020 г., 23:28 Denis Magda <dma...@apache.org> <
dma...@apache.org>:
Alex, thanks for helping with the documentation. Frankly, the
tickets
will be useful to get a complete list of all the updates pages
with
the
goal of extracting info for blog post(s) - we'll be
preparing at
least
one
blog for Ignite 2.8 and can create an ML specific blog as well.
Also,
the
tickets might simplify the review process between you and
Artem.
-
Denis
On Sat, Feb 22, 2020 at 2:18 AM Alexey Zinoviev <
zaleslaw....@gmail.com
wrote:
I've created a draft pages on apache.readme.io and will
continue
my
work there during next 2 weeks.
Should I create any tickets for that? Or could miss that step?
Will notify in this thread than the work will be done!
чт, 20 февр. 2020 г. в 12:16, Alexey Zinoviev <
zaleslaw....@gmail.com
:
Yes, there are a lot of changes in ML from 2.7, I'm going to
prepare
new documentation and create documentation related tickets for
the
ML
component.
After some consultation and review from Artem side I'll add new
documentation on readme.io.
чт, 20 февр. 2020 г. в 02:34, Denis Magda <dma...@apache.org>
<
dma...@apache.org>:
Artem,
Thanks for stepping in and preparing the list of top priority
documentation tasks! How about labeling those tickets somehow
and
creating
a filter similar to this one [1] but for "Required &
Unresolved
Documentation Tasks"? I would simply add this as a new
section to
the
Ignite 2.8 release wiki page for ease of tracking and start
working
with
the guys contributed improvements directly. Will see the
names of
the
authors who need to be involved ;)
*Alexey Zinoviev*, there are many ML related changes coming in
the
release. Could you check existing ML docs and suggest any
changes?
[1]
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolveddocumentationtasks
-
Denis
On Wed, Feb 19, 2020 at 11:14 AM Artem Budnikov <
a.budnikov.ign...@gmail.com> wrote:
Maxim,
One note from my side, I think we can move disk page
compression
[1]
to the 2-nd priority, but definitely must document WAL page
compression first [2]
OK, good to know.
On Wed, Feb 19, 2020 at 6:48 PM Maxim Muzafarov <
mmu...@apache.org>
wrote:
Artem,
Thank you for starting this thread.
One note from my side, I think we can move disk page
compression
[1]
to the 2-nd priority, but definitely must document WAL page
compression first [2]
The list of important tasks [3].
The list of documentation tasks [4].
[1] https://issues.apache.org/jira/browse/IGNITE-10330
[2] https://issues.apache.org/jira/browse/IGNITE-11336
[3]
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Themostimportantreleasetasks
[4]
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolveddocumentationtasks
On Wed, 19 Feb 2020 at 18:15, Artem Budnikov<
a.budnikov.ign...@gmail.com> <a.budnikov.ign...@gmail.com> wrote:
Hi everyone,
As the release of Ignite 2.8 is getting closer, let's
discuss
which
features should be documented. I created a list of features
based
on the
release notes and the documentation tickets in jira (see
below).
Much more
has been added, but these seemed to have first priority.
It's
not
to say
that other features are not important, but given the
limited
resources a
list of high-priority task would help to schedule the time
of
those
who
will help with the docs.
Here is the list of features:
Disk page compression
Metrics and System Views documentation
Default Ignite work dir location
Baseline auto-adjust feature
Cluster (de)activation events documentation
Remove SqlQuery documentation
Partition awareness for thin clients
Transactions support in thin clients
KILL QUERY command
Move rebalance configuration properties to the
IgniteConfiguration level
Renamed IGNITE schema to SYS
JDBC: Support for query cancellation
JDBC: Support for query timeout
suspend/resume for pessimistic transactions
Now, two really big questions here:
If you want to add anything else to the documentation,
please
let
us
know in this thread.
If you are the author of any of the features listed
above,
please
share
the details on the feature. You can do it by creating a
documentation
ticket. If you want to contribute a page or section to the
existing
docs,
you can write directly on apacheignite.readme.io (send me
a
note
if you
don't have an account there). Any help is greatly
appreciated.
-Artem
