Correct. This page shouldn't be published.
-Artem
On Thu, Mar 19, 2020 at 5:35 PM 18624049226 <18624049...@163.com> wrote:
> Hi Artem,
>
> https://apacheignite.readme.io/docs/partition-map-exchange-27
>
> This page has no corresponding menu link, is it correct?
>
> 在 2020/3/17 上午12:47, Denis
Hi Artem,
https://apacheignite.readme.io/docs/partition-map-exchange-27
This page has no corresponding menu link, is it correct?
在 2020/3/17 上午12:47, Denis Magda 写道:
Artem,
I'll create a ticket for the IGFS docs replacement once we publish the new
website that we'll have all the references
Artem,
I'll create a ticket for the IGFS docs replacement once we publish the new
website that we'll have all the references needed to create new pages that
will replace the IGFS content.
@Yuriy Gerzhedovich , could you please help
with the SQL questions?
-
Denis
On Mon, Mar 16, 2020 at 12:22
Can anyone give some details about those missing features so I can
document them?
-Artem
On 15.03.2020 05:31, 18624049226 wrote:
Hi,
I don't know the missing part. Is there any developer willing to add it?
In addition, as far as I know, IGFS and Hadoop accelerator related
components of
Hi,
I don't know the missing part. Is there any developer willing to add it?
In addition, as far as I know, IGFS and Hadoop accelerator related
components of ignite have been discarded, should related documents also
be deleted?
在 2020/3/13 上午6:08, Ivan Pavlukhin 写道:
Hi,
There are the
Hi,
> There are the following functions. I haven't found the related documents.
> Please confirm again?
Thank you for checking this thoroughly! I looked into SQL and JDBC items.
> 1.SQL:Added KILL QUERY command
Here it is https://apacheignite-sql.readme.io/docs/kill-query but it
seems no link
Hi igniters,
There are the following functions. I haven't found the related
documents. Please confirm again?
1.SQL:Added KILL QUERY command
2.SQL:Added ability to specify query parallelism in CREATE TABLE's WITH
"" clause
3.SQL:Added default query timeout
4.JDBC:Added cache expiry
Denis,
I made version 2.8 the main version on readme.io. Everybody can see it now.
-Artem
On Wed, Mar 11, 2020 at 7:35 PM Denis Magda wrote:
> Artem,
>
> Understood, let's see what Alexey says. As of now, I would suggest we
> publishing the existing ML pages and improve the content with no
Artem,
Understood, let's see what Alexey says. As of now, I would suggest we
publishing the existing ML pages and improve the content with no rush.
Could you also make a 2.8 version the default one? 2.7.6 is still selected
by default when I navigate to the documentation website.
-
Denis
On
Denis,
I'm waiting for answers from Alexey. I can't really tell how lont it will
take. Of couse, we can publish everything right now and improve some pages
later.
-Artem
On Wed, Mar 11, 2020 at 7:13 PM Denis Magda wrote:
> Artem, thanks! How much time should it take to roll out the ML pages?
Denis,
Oh, so many synchronizations locks :-)
I'll wait, of course, please, let me know when the post happens.
On Wed, 11 Mar 2020 at 19:13, Denis Magda wrote:
>
> Artem, thanks! How much time should it take to roll out the ML pages? Can
> we release what's available right now and continue
Artem, thanks! How much time should it take to roll out the ML pages? Can
we release what's available right now and continue improving the pages in
parallel?
Maxim, please let me publish the blog post [1] on the apache website before
sending you'll send an announcement email. The article will
Artem, Folks
Thank you all.
I'll do announce the release tomorrow in the middle of the day (~16.00 MSK TZ).
On Wed, 11 Mar 2020 at 16:06, Artem Budnikov
wrote:
>
> I created the Apache Ignite Documentation 2.8 with all the new pages except
> for ML, which I and Alexey are still working on.
I created the Apache Ignite Documentation 2.8 with all the new pages except
for ML, which I and Alexey are still working on. The docs are not published
yet, but you can see them under version 2.8.0 if you log into readme.io.
The ML pages could take a while, but other than that the initial plan on
OK, I'm going to create the 2.8 version on readme.io for all documentation
pages. If anyone is still working on the docs version 2.7.6, please let me
know. I'll post an update in this thread when I finish. Further changes
should be made in version 2.8.
-Artem
On Wed, Mar 11, 2020 at 10:16 AM
Artem,
I've updated the Read Repair page
On Thu, Mar 5, 2020 at 3:51 PM Artem Budnikov
wrote:
> 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.
> • Looks like this sentence should contain a link to somewhere: "Please, see
> XXX as an example and OpenCensus documentation for additional information."
Fixed.
> • Please mention that for the OpenCensus exporter to work, the module
> should be enabled.
Fixed.
> • Also,
Hi Nikolay,
I looked through the metrics pages and found a couple of minor issues:
* Looks like this sentence should contain a link to somewhere:
"Please, see XXX as an example and OpenCensus documentation for
additional information."
* Please mention that for the OpenCensus exporter to
Folks,
It seems everything is ready to go and only minor issues left with
documentation.
Are we ready to announce 2.8 release widely?
On Tue, 10 Mar 2020 at 12:10, Nikolay Izhikov wrote:
>
> Hello, Igniters.
>
> I rewrote pages about new metrics and system views.
> Please, take a look.
>
>
Hello, Igniters.
I rewrote pages about new metrics and system views.
Please, take a look.
https://apacheignite.readme.io/docs/new-metrics
https://apacheignite.readme.io/docs/system-views
https://issues.apache.org/jira/browse/IGNITE-12408
> 6 марта 2020 г., в 16:40, Artem Budnikov
>
Anton,
Thanks for the feedback. I updated the page.
-Artem
On 05.03.2020 16:32, Anton Vinogradov wrote:
Artem, great!
Some minors:
read operations become more costly for caches with backup copies.
Since it makes sense only for cache with backups, can we say something like
"read operations
Artem, great!
Some minors:
>> read operations become more costly for caches with backup copies.
Since it makes sense only for cache with backups, can we say something like
"read operations become at least 2 times costly since backups checked as
well"
>> for atomic caches, a consistency
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
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
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 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
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
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]
> 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 :
>
> Maxim,
>
> Yes, it's
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.
I think yes.
I will prepare documentation shortly.
> 4 марта 2020 г., в 17:50, Maxim Muzafarov написал(а):
>
> 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,
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 wrote:
>
> The only feature that is left is "WAL page compression"
>
> The three other features are
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
>
> 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
Artem,
IEP [1] answers this in detail, but in brief...
Cons:
- each get() cost, when RR used, increased by requests to each backup,
- read from backup, near cache and external store usage are impossible.
Pros:
- consistency may be checked online (no need to turn off the cluster),
- consistency
Anton,
Yes, I can add this feature to the docs. I have a couple of questions,
though:
* Are there any downsides to using this feature?
* When users should use it? What are the recommendations?
-Artem
On 04.03.2020 13:46, Anton Vinogradov wrote:
Artem,
Is it possible to create
Artem,
Is it possible to create documentation for ReadRepair feature [1] [2]?
Feature marked as @IgnireExperimenta but ready to be used.
Javadoc [3] explains the details.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-31+Consistency+check+and+fix
[2]
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
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
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).
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
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
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
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
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
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
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
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 :
> Ok, will make ticket, no problemo
>
> вс, 23 февр. 2020 г., 23:28 Denis Magda :
>
>> Alex, thanks for
Ok, will make ticket, no problemo
вс, 23 февр. 2020 г., 23:28 Denis Magda :
> 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
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
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 :
> Yes, there are a lot of
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 :
>
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
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 wrote:
> Artem,
>
>
> Thank you for starting this thread.
> One
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]
53 matches
Mail list logo
