Hi Everyone,
I posted an instruction on how to publish the docs on ignite.apache.org/docs
[1]. When you finish with Ignite 2.9, you can update the docs by following
the instruction. Unfortunately, I won't be able to spend any time on this
project any longer. You can send your pull requests and que
to the footer of the pages?
>>
>> *© 2020 The Apache Software Foundation.*
>> *Apache, Apache Ignite, the Apache feather and the Apache
Ignite logo are
>> either registered trademarks or trademarks of The Apache Software
>> Foundation.
ng of something along a blue circle with `i' in it, for
information items.
Regards,
--
Ilya Kasnacheev
ср, 19 авг. 2020 г. в 18:29, Artem Budnikov <
a.budnikov.ign...@gmail.com
:
Search does not seem to work.
It uses mockups right now, but it should be ready when the docs are
rele
I've created a JIRA issue:
https://issues.apache.org/jira/browse/IGNITE-13388
-Artem
On 27.08.2020 12:05, Petr Ivanov wrote:
Hi, Artem,
Can you file and issue with description what exactly do not work and
why, please?
On 27 Aug 2020, at 11:55, Artem Budnikov <mailto:a.budn
Artem Budnikov created IGNITE-13388:
---
Summary: apache-ignite deb package depends on the non-existent
package and can't be installed on Debian 10
Key: IGNITE-13388
URL: https://issues.apache.org/jira/b
Looks like this issue wasn't fixed in 2.8.1. The Ignite deb package v.
2.8.1 can't be installed on debian 10:
$ sudo apt-get install apache-ignite
...
The following packages have unmet dependencies:
apache-ignite : Depends: openjdk-8-jdk but it is not installable or
ora
Search does not seem to work.
It uses mockups right now, but it should be ready when the docs are
released.
I can see that note blocks are just annotated with "Note." Can we have some
image there?
Do you have a preference as to which image you would like to see there?
-Artem
On 19.08.2020 1
Hi everyone,
We've set up a staging site for the Ignite 2.9 docs:
http://64.227.57.229/docs/2.9.0/installation/installing-using-docker
user/pass: ignite/apache2020
More content is being added, but that's basically what it will look like.
Your comments are welcome.
-Artem
On 18.08.2020 22:0
Hi Everyone,
I looked at the documentation tasks for Ignite 2.9 [1] and noticed that
some of them were being worked on. I'll take a look at the other tickets
(unassigned or assigned to me). I hope I'll have enough time to finish
them by the time of the release.
-Artem
[1]:
https://cwiki.ap
ould suggest contributing 2.9 related page to the new
documentation
repository.
Denis
On Monday, August 3, 2020, Artem Budnikov
Hi Maxim,
The new docs project is not finished yet. There are still a lot of
pages
to port to the new format, and we are still working on the
integration
with
t
for 2.9 release. Should
I update docs on readme.io or publish it on ignite.apache.org?
On Wed, 29 Jul 2020 at 19:06, Artem Budnikov
wrote:
Hi Alex,
Sorry, I missed this message. There is still a lot of work on the docs.
When is version 2.9 going to be released?
-Artem
On 22.07.2020 10:35, Alex
ignite.apache.org?
What about new edits? Should we still edit pages on readme.io or already
make changes in git repository?
Artem, could you please clarify the current documentation workflow?
пн, 20 июл. 2020 г. в 16:42, Artem Budnikov :
Denis,
How about the next step of taking the HTML and committing it
on my end. Thanks for sending the update!
How about the next step of taking the HTML and committing it to the website
repository? Did you have a chance to think through this step?
-
Denis
On Fri, Jul 17, 2020 at 5:27 AM Artem Budnikov
wrote:
Hi everyone,
I've prepared the initial set of s
keeps docs for it's products in
separate repos, for example.
On Thu, 25 Jun 2020 at 15:48, Artem Budnikov
wrote:
OK, let's give it a try.
The way I see it, the documentation source files will be located in the
"/docs" folder, including UI templates/styles, asciidoc files,
Kondakov
On 16.07.2020 14:19, Ilya Kasnacheev wrote:
Hello!
The Project Management Committee for Apache Ignite project has invited
Artem Budnikov to become a committer and we are pleased to announce that
he
has accepted.
He is the person behind a monumental effort to keep Apache Ignite
documentation
e documentation merge the changes first and ask for a review later if
needed.
-
Denis
On Tue, Jun 23, 2020 at 6:53 AM Artem Budnikov
wrote:
Pavel,
I don't think so: we can't add snippets pointing to new APIs from a
separate repo,
Snippets are kept together with the docs, they /don&#x
repo will require separate ownership/management
(probably?),
but we already have everything in the main repo, why introduce overhead?
On Tue, Jun 23, 2020 at 2:59 PM Artem Budnikov
mailto:a.budnikov.ign...@gmail.com>> wrote:
Pavel,
As far as I can see, all your pros points work j
Code snippets can be tested on TC
GridGain uses a separate repo for their docs, and it proved to be less than
optimal.
Especially when adding samples for new APIs which are not yet released.
On Tue, Jun 23, 2020 at 1:19 PM Artem Budnikov
wrote:
Pavel,
Yes, I mean a separate repository. The r
Pavel,
Yes, I mean a separate repository. The reason is that documentation is
usually updated after the product version is released. As Ilya pointed
out, keeping the docs in the main Ignite repository would entail
completing the docs before the release date, which is not possible under
curren
Hello Igniters,
I'd like to return to the discussion about migrating the Ignite
documentation from readme.io to github. The idea emerged long time ago
[1] but hasn't been implemented. I think now is the time to make it happen.
Here are the technical details of the proposed solution:
* docs
> >
> > @Yuriy Gerzhedovich , could you please help
> > with the SQL questions?
> >
> > -
> > Denis
> >
> >
> > On Mon, Mar 16, 2020 at 12:22 AM Artem Budnikov <
> a.budnikov.ign...@gmail.com>
> > wrote:
> >
> >>
rts, is it missing?confirm again?
>
> thank you very much!
>
> 在 2020/3/19 下午3:41, Artem Budnikov 写道:
> > Hi,
> >
> > Please find the archive with the latest docs attached.
> >
> > -Artem
> >
> > On Thu, Mar 19, 2020 at 6:32 AM 18624049226 &l
Denis,
Both yours and Andrey's proposal are important. You should start to vote
after the documentation is ready, just like you start to vote after all
features are ready, and documentation is just another feature. However, the
documentation can't be prepared if there is no information on the feat
"top" command
9.REST:Added baseline topology commands to REST API
10.REST:Added memory policy metrics via REST
These are great improvements, and without documentation, developers may
not know how to use them.
在 2020/3/12 上午1:40, Artem Budnikov 写道:
Denis,
I made version 2.8
e 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 Wed, Mar 11, 2020 at 9:33 AM Artem Budnikov <
> a.budnikov.ign...@gmail.com>
>
rov wrote:
>
> > 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:
> >
creating the docs is accomplished, so it's no longer an obstacle to
announcing the release.
-Artem
On Wed, Mar 11, 2020 at 11:50 AM Artem Budnikov
wrote:
> OK, I'm going to create the 2.8 version on readme.io for all
> documentation pages. If anyone is still working on the do
t 10:16 AM Anton Vinogradov wrote:
> 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.
ira/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
d violation triggers event with type ==
org.apache.ignite.events.EventType#EVT_CONSISTENCY_VIOLATION includes
org.apache.ignite.events.CacheConsistencyViolationEvent which should be
used for rechecking of repait results.
On Thu, Mar 5, 2020 at 3:51 PM Artem Budnikov
wrote:
Anton,
Could you please r
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&#
reated 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 some pages un
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 ple
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 limitations th
cs &
monitoring? @Nikolay
Izhikov how soon will you be able to finish the
metrics documentation pages?
-
Denis
On Wed, Mar 4, 2020 at 2:55 AM Artem Budnikov
wrote:
Hi everyone,
I have created the docs for the following items so far:
-Default Ignite work dir location
https://apa
://issues.apache.org/jira/browse/IGNITE-11978
On Wed, Mar 4, 2020 at 1:15 PM Artem Budnikov
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
h the Metrics and System Views documentation?
Artem Budnikov
Technical Writer
gridgain.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
- Renamed IGNITE schema to SYS
done
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
nts 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
+2.8#ApacheIgnite2.8-Unresolveddocumentationtasks
>
> On Wed, 19 Feb 2020 at 18:15, Artem Budnikov
> 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
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
Hi Sergey,
Please create a ticket for documentation update as described in this
section:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Documentingaticket
-Artem
On 07.02.2020 12:00, Sergey Chernolyas wrote:
Hi igniters!
Feature, which I working on, re
Hi everyone,
I think a link to the documentation is unnecessary. We could simply
mention "baseline topology", and users will be able to find what it is
in the docs.
Artem Budnikov
Technical Writer
gridgain.com
On 13.01.2020 21:15, Denis Magda wrote:
Stan,
I would not suggest us
Hi Maxim,
I'm glad to see that you care about documentation. Way to go! Here is a
couple of points that can help:
1) I think it's safe to assume that Prachi will not work on the Ignite
documentation any longer. You can take up the issues assigned to her and
prioritize them whichever way is c
Hi,
I've created new versions for other projects on readme.io
-Artem
On 18.09.2019 19:17, Alexey Goncharuk wrote:
Igniters,
I am following the release process procedure [1] and currently on docs
update step. I can login to the admin panel, but I can only see the main
Ignite docs project. Who
p 13, 2019 at 7:05 AM Artem Budnikov
mailto:a.budnikov.ign...@gmail.com>> wrote:
Hi Denis,
I updated the page about eviction policies. Not freeing up space
on disk was not implemented for reasons explained in the dev-list
thread. I'll update the page once
Hi Denis,
I updated the page about eviction policies. Not freeing up space on disk
was not implemented for reasons explained in the dev-list thread. I'll
update the page once more if/when a solution is implemented.
Artem
On 13.09.2019 00:34, Denis Magda wrote:
Shiva,
Hopefully, someone fro
Hi Maxim,
Please create a documentation ticket as described here [1] or here [2].
Garrett, this improvement will be released in Ignite 2.8.
[1]:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-Basics
[2]:
https://cwiki.apache.org/confluence/display/IGNITE
Hi everyone,
Re Issue 3:
That's a good idea, but as far as I remember this was done in
https://jira.apache.org/jira/browse/IGNITE-10279 and is waiting to be
released in Ignite 2.8.
-Artem
On 26.08.2019 15:18, Anton Kalashnikov wrote:
Hello, Igniters.
+1 for Script help usability - issue 3
Hi Dmitry,
The release notes reviewed. Please see my comment in the pull request.
-Artem
On 19.08.2019 14:20, Dmitriy Pavlov wrote:
Hi Andrey,
could you please take a look at
https://issues.apache.org/jira/browse/IGNITE-12061 ?
Are you comfortable with merging it to release (in rush mode)?
Guys,
I updated the page.
-Artem
On 02.06.2019 22:20, Nikolay Izhikov wrote:
Hello, Denis.
Ignite doesn't encrypt memory page as long as it retains in memory.
Page encrypted when it is written to the disk.
пт, 31 мая 2019 г. в 19:39, Denis Magda :
Nikolay,
Do we really support encryption
Artem Budnikov created IGNITE-10868:
---
Summary: WAL segments are removed from WAL archive after each
checkpoint
Key: IGNITE-10868
URL: https://issues.apache.org/jira/browse/IGNITE-10868
Project
Artem Budnikov created IGNITE-10850:
---
Summary: Clarify the use of the enforceJoin flag
Key: IGNITE-10850
URL: https://issues.apache.org/jira/browse/IGNITE-10850
Project: Ignite
Issue Type
Artem Budnikov created IGNITE-10154:
---
Summary: Critical worker liveness check configuration is
non-trivial and inconsistent
Key: IGNITE-10154
URL: https://issues.apache.org/jira/browse/IGNITE-10154
Hi Igniters,
Please take a look at the changes in the "How to Contribute" procedure
[1] related to Ignite documentation. I just reflected there what we
discussed earlier about our documentation process. Please see this
thread for more information [2].
[1]:
https://cwiki.apache.org/confluen
Hi Pavel,
1) I fixed the broken link. Thanks for pointing out.
2) Yes, that is a common problem, and as far as I know, we don't have
such a check, but we will when we adopt the new docs publishing process
(markdown-to-html-pulled-from-github-based process).
Cheers,
Artem
On 25.10.2018 16:36
Artem Budnikov created IGNITE-9245:
--
Summary: Document how to monitor Ignite with Zabbix
Key: IGNITE-9245
URL: https://issues.apache.org/jira/browse/IGNITE-9245
Project: Ignite
Issue Type
not, please sign up
and share your wiki login (id).
Sincerely,
Dmitriy Pavlov
вт, 24 июл. 2018 г. в 10:25, Artem Budnikov
mailto:a.budnikov.ign...@gmail.com>>:
Hi everyone,
Despite what I've been told about INFRA, it responded
exceptional
;
needs to be updated to reflect the changes related to documentation
process. Could someone do this?
Cheers,
Artem
On 23.07.2018 18:00, Artem Budnikov wrote:
Hi everyone,
I created an issue in the Apache INFRA project:
https://issues.apache.org/jira/browse/INFRA-16803
Cheers,
Artem
On
fit of having "Docs Required" flag enabled by default, is
that
Artem and Prachi can see all such tickets months and weeks before a
release, figure out details from source code contributors and complete
the
docs in advance.
--
Denis
On Wed, Jul 18, 2018 at 8:39 AM Artem Budnikov <
a.b
, please share your thoughts.
If you are concerned that it's not possible to add a field, then we
should contact Apache Infra and find out.
Best regards,
Artem Budnikov
On 18.07.2018 16:14, Dmitry Pavlov wrote:
Hi Artem,
I sometimes receive feedback that Ignite docs has potentia
tickets, and
3. issues that require documentation but have no related issues (which
means that the author forgot to create a documentation issue for it).
Please share your thoughts about this.
Best regards,
Artem Budnikov
62 matches
Mail list logo
