Nikita, let me disagree with you.
Although, nested commands seem to be overcomplicated, they are widely used in
industry in tools like GIT, DOCKER, K8S, etc.
May be I am wrong, but it looks like that professional engineering community
has already get used to them and such syntax would not be a
Hi, Denis.
Apache Ignite as other projects on Apache is in fact released from TAG, not
BRANCH (although they are similar at that point).
Thus — it seems that there should be no problem to continue using branch as
docs sources for the same release as long as TAG stays intact.
We just have to
Ivan Daschinskiy created IGNITE-13882:
-
Summary: Support configurable install root and work root for
ducktape
Key: IGNITE-13882
URL: https://issues.apache.org/jira/browse/IGNITE-13882
Project:
When it comes to CLI commands - I would highly recommend to stick to a
traditional Unix/Linux approach of command line interfaces and REPLs (i.e.
command + zero or more parameters). Nested commands are not a good idea
IMHO as they are very hard to document or remember. aws-cli or az have them
-
Igniters,
After we release a version, we create a docs-specific branch out of the
release branch for inevitable documentation improvements (feedback; generic
changes that are committed to the master, and the last published version).
For instance, once 2.9 was released from the "ignite-2.9"
Denis A. Magda created IGNITE-13881:
---
Summary: Set up redirects from readme.io to the new Ignite docs
Key: IGNITE-13881
URL: https://issues.apache.org/jira/browse/IGNITE-13881
Project: Ignite
Certainly, the end of Jan is more realistic and reasonable. Let's talk this
out offline and then put a session on the virtual meetup's schedule.
-
Denis
On Sun, Dec 20, 2020 at 4:35 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Hi Denis,
>
> Sure, that's a great idea! I'm
Hey.
1. Sure, will remove demo suffixes.
2. I thought about it. Not sure why “node-start” is better than “node
start”.
In general, we really have a subcommands hierarchy and I think it is ok not
to hide it.
Many tools with subcommands use the same approach: az (azure), aws, docker,
kubectl,
Hi, Igniters.
We all know that the current QueryEntity API is not convenient and needs to
be reworked.
So, I'm glad to share PR [1] with schema configuration public API for
Ignite 3.0.
New schema configuration uses Builder pattern, which looks more comfortable
to use.
In the PR you will find a
Aleksey Plekhanov created IGNITE-13880:
--
Summary: Flaky PageMemoryTracker related tests
Key: IGNITE-13880
URL: https://issues.apache.org/jira/browse/IGNITE-13880
Project: Ignite
Issue
Pramod Patwa created IGNITE-13879:
-
Summary: ignite-rest-http is not working with spring data rest
Key: IGNITE-13879
URL: https://issues.apache.org/jira/browse/IGNITE-13879
Project: Ignite
Ilya Kasnacheev created IGNITE-13878:
Summary: Allocated RAM is always 0 for non-persistent regions of
persistent cluster
Key: IGNITE-13878
URL: https://issues.apache.org/jira/browse/IGNITE-13878
12 matches
Mail list logo
