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
+1.
> 23 июня 2020 г., в 10:02, Artem Budnikov
> написал(а):
>
> 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
I'd like this approach, it's easier for contributors to suggest edits.
+1
вт, 23 июн. 2020 г. в 10:03, Nikolay Izhikov :
> +1.
>
> > 23 июня 2020 г., в 10:02, Artem Budnikov
> написал(а):
> >
> > Hello Igniters,
> >
> > I'd like to return to the discussion about migrating the Ignite
> documentat
+1
For now it's unclear how to add new pages to the site. I hope it'll be
a clear process.
вт, 23 июн. 2020 г. в 10:06, Alexey Zinoviev :
>
> I'd like this approach, it's easier for contributors to suggest edits.
> +1
>
> вт, 23 июн. 2020 г. в 10:03, Nikolay Izhikov :
>
> > +1.
> >
> > > 23 июня 2
Ok, I changed agents requirements to builds and add them to runAll
пн, 22 июн. 2020 г. в 22:39, Petr Ivanov :
> Cmake is installed on all agents (except 10 which is currently down and
> will be updated later).
>
>
> > On 22 Jun 2020, at 21:03, Ivan Daschinsky wrote:
> >
> > Well, patch is merged
Ivan Daschinskiy created IGNITE-13176:
-
Summary: C++: Remove autotools build after merging CMake
Key: IGNITE-13176
URL: https://issues.apache.org/jira/browse/IGNITE-13176
Project: Ignite
Thomas Landuyt created IGNITE-13177:
---
Summary: Upgrade Zookeeper version to 3.5.7 or higher
Key: IGNITE-13177
URL: https://issues.apache.org/jira/browse/IGNITE-13177
Project: Ignite
Issue T
+1
> stored in a github repository
Do you mean a separate repository here?
I think we should use the main Ignite repo for documentation.
On Tue, Jun 23, 2020 at 10:21 AM Nikita Amelchev
wrote:
> +1
> For now it's unclear how to add new pages to the site. I hope it'll be
> a clear process.
>
>
Hello!
I'm not really sold on the github version yet, I would like to see a
prototype of such documentation before deciding, so for me it'w
0
Pavel, we don't have enough discipline to make sure that all documentation
is ready at the time of release, and we may need to add notices here and
there a
Well, new suites added to RunAll and all seems to be ok.
I think it is time to remove old suites.
WDYT?
Also, I created patch with removal of autotools, but old suites should be
removed first.
So, folks, is it ok to remove old suites from build chain?
вт, 23 июн. 2020 г. в 10:36, Ivan Daschinsk
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
> So, folks, is it ok to remove old suites from build chain
+1 from me.
> 23 июня 2020 г., в 13:15, Ivan Daschinsky написал(а):
>
> Well, new suites added to RunAll and all seems to be ok.
>
> I think it is time to remove old suites.
> WDYT?
>
> Also, I created patch with removal of autotool
Ilya, Artem,
"Separate repo just because we can't finish docs before release"
does not make sense to me. My proposal is:
- Working version is in the master branch
- When a release branch is created, e.g. ignite-2.9, we create
ignite-2.9-docs and update it as long as we want.
Pros (compared to a
Pavel,
As far as I can see, all your pros points work just as well for a
separate repository (except for "everybody knows about it"). I don't
mind keeping the docs in Ignite repo as long as I am able to freely
commit to master. Will I be able to do that?
-Artem
On 23.06.2020 14:04, Pavel Tu
Ameer Basha Pattan created IGNITE-13178:
---
Summary: Spark job gets stuck indefinitely while trying to fetch
data from ignite cluster using thin client
Key: IGNITE-13178
URL: https://issues.apache.org/jira/bro
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't need/ to be stored
in the main repo, although they can. They are compilable and up to date.
I update the docs and API samples for features that hasn't
+1 to keep docs and sources together.
-1 to keep docs in external repository.
> 23 июня 2020 г., в 16:47, Artem Budnikov
> написал(а):
>
> 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't
For the sake of discretion, I'd purpose to remove old suites from Run All and
archive or pause them for some time before removal.
> On 23 Jun 2020, at 13:26, Nikolay Izhikov wrote:
>
>> So, folks, is it ok to remove old suites from build chain
>
> +1 from me.
>
>
>> 23 июня 2020 г., в 13:15
>> For the sake of discretion, I'd purpose to remove old suites from Run
All and archive or pause them for some time before removal.
Agree, I was talking about removal from RunAll chain, complete removal is
not necessary.
But after private discussion with Igor Sapego, me and he decided to wait
for
Petr, I see, that cmake is missing on aitc10_05 but it is in pool and
trying to run build.
[1] --
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCPPCMakeLinux/5412025
вт, 23 июн. 2020 г. в 17:33, Ivan Daschinsky :
> >> For the sake of discretion, I'd purpose to remove
That host was down for some time and got up only recently.
Installed cmake there also.
> On 23 Jun 2020, at 17:39, Ivan Daschinsky wrote:
>
> Petr, I see, that cmake is missing on aitc10_05 but it is in pool and
> trying to run build.
>
> [1] --
> https://ci.ignite.apache.org/buildConfigurati
Hello, Alexey!
I suggest that we decide what we can do within ticket [1].
Add "rebalanceId" and "topVer" related to rebalance to all messages.
Add statistical information to a log message:
[2020-05-06 20:56:37,044][INFO ][...] Completed rebalancing [rebalanceId=1,
grp=cache1,
supplier=94a3fcbc-
Hi, Kirill.
Looks good to me.
вт, 23 июн. 2020 г. в 18:05, ткаленко кирилл :
> Hello, Alexey!
>
> I suggest that we decide what we can do within ticket [1].
>
> Add "rebalanceId" and "topVer" related to rebalance to all messages.
>
> Add statistical information to a log message:
> [2020-05-06 20
Hello!
Once you do that, I think it would make sense to remove autotools
invocation from artifact build process. In the future we may choose to
remove autotools support entirely.
Regards,
--
Ilya Kasnacheev
вт, 23 июн. 2020 г. в 18:00, Petr Ivanov :
> That host was down for some time and got
I suppose, that removal of autotools from source code is a question of a
week. There is no need to support it.
вт, 23 июн. 2020 г., 18:38 Ilya Kasnacheev :
> Hello!
>
> Once you do that, I think it would make sense to remove autotools
> invocation from artifact build process. In the future we may
Hello Maxim, folks,
ср, 6 мая 2020 г. в 21:01, Maxim Muzafarov :
> We won't do performance analysis on the production environment. Each
> time we need performance analysis it will be done on a test
> environment with verbose logging enabled. Thus I suggest moving these
> changes to a separate `pr
Hello, Alexey!
Currently there is no way to disable / enable it, but it seems that the logs
will not be overloaded, since Alexei Scherbakov offer seems reasonable and
compact. Of course, you can add disabling / enabling statistics collection via
jmx for example.
23.06.2020, 18:47, "Alexey Gonc
Taras Ledkov created IGNITE-13179:
-
Summary: Calcite integration. Fix traits at the IgniteLimit
Key: IGNITE-13179
URL: https://issues.apache.org/jira/browse/IGNITE-13179
Project: Ignite
Issue
Sergei Ryzhov created IGNITE-13180:
--
Summary: AuthenticationContext should contain the address when
connecting the IgniteClient and using IgniteSecurity
Key: IGNITE-13180
URL: https://issues.apache.org/jira/brows
I believe that by keeping the documentation sources in the same repository
with the source code will help us to prepare and release all the release
artifacts at the same time. So, +1 for hosting raw documentation ascii-doc
pages in the main Ignite repo. However, the HTML version needs to reside on
Excellent. Let me know if my version of the message works for you. Shared
it in the pull-request.
-
Denis
On Fri, Jun 19, 2020 at 3:15 AM Taras Ledkov wrote:
> Hi,
>
> I change the error message [1].
> The suggestion at the message contains info about requirement to remove
> all data with old
Semyon,
Thanks for highlighting this ticket on the dev list. I've joined the
discussion in JIRA.
-
Denis
On Mon, Jun 22, 2020 at 2:41 AM Данилов Семён wrote:
> Hello igniters!
>
> I've been working on a tutorial regarding Spring Cloud + Ignite and came
> across this issue:
>
> IgniteRepositor
32 matches
Mail list logo
