ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Artem Budnikov <abudni...@gridgain.com>
Subject Re: Ignite 2.8 documentation
Date Tue, 03 Mar 2020 14:02:24 GMT
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 Writer
gridgain.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.sin@gmail.com 
> <mailto:zaleslaw.sin@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 page
>     https://dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees
>     and
>     moved it under new page
>     https://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 <dmagda@apache.org
>     <mailto:dmagda@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 <
>     > prasadbhalerao1983@gmail.com
>     <mailto:prasadbhalerao1983@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.sin@gmail.com <mailto:zaleslaw.sin@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.sin@gmail.com <mailto:zaleslaw.sin@gmail.com>
>     > >:
>     > > >
>     > > > > Ok, will make ticket, no problemo
>     > > > >
>     > > > > вс, 23 февр. 2020 г., 23:28 Denis Magda <dmagda@apache.org
>     <mailto:dmagda@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.sin@gmail.com <mailto:zaleslaw.sin@gmail.com>
>     > > > >
>     > > > >> wrote:
>     > > > >>
>     > > > >>> I've created a draft pages on apache.readme.io
>     <http://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.sin@gmail.com <mailto:zaleslaw.sin@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 <http://readme.io>.
>     > > > >>>>
>     > > > >>>>
>     > > > >>>>
>     > > > >>>> чт, 20 февр. 2020 г. в 02:34, Denis Magda
>     <dmagda@apache.org <mailto:dmagda@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.ignite@gmail.com
>     <mailto:a.budnikov.ignite@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
<
>     > > mmuzaf@apache.org <mailto:mmuzaf@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.ignite@gmail.com
>     <mailto:a.budnikov.ignite@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
>     <http://apacheignite.readme.io> (send me a
>     > > note
>     > > > >>>>>> if you
>     > > > >>>>>> > don't have an account there). Any help
is greatly
>     appreciated.
>     > > > >>>>>> > >
>     > > > >>>>>> > > -Artem
>     > > > >>>>>> > >
>     > > > >>>>>> > >
>     > > > >>>>>> >
>     > > > >>>>>>
>     > > > >>>>>
>     > > >
>     > >
>     >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message