Alex, Nikolay, thanks! Forgive me for my poor googling skills ;)
-
Denis
On Fri, Oct 18, 2019 at 7:26 AM Alex Plehanov
wrote:
> Documentation for views released in 2.7 is here:
> https://apacheignite-sql.readme.io/docs/system-views
>
> пт, 18 окт. 2019 г. в 17:24, Nikolay Izhikov :
>
> > Denis
Documentation for views released in 2.7 is here:
https://apacheignite-sql.readme.io/docs/system-views
пт, 18 окт. 2019 г. в 17:24, Nikolay Izhikov :
> Denis, AFAIK we doesn't have documentation for the SQL System Views
> existing in Ignite.
>
> I have plans to write a documentation about metrics
Denis, AFAIK we doesn't have documentation for the SQL System Views existing in
Ignite.
I have plans to write a documentation about metrics and syste views that will
cover SQL System View.
It will be available till 2.8 release.
В Пт, 18/10/2019 в 07:16 -0700, Denis Magda пишет:
> Alex, Ignite
Alex, Igniters,
Who of us was contributing this feature? I don’t see any documentation, not
clear how the users are expected to benefit from the capability and how
everybody will be aware of the feature existence.
We need to close the gap and spread the word.
Denis
On Thursday, October 17, 2019
Denis,
Views engine and some views were released in AI 2.7.
In 2.8 they will be moved to the new engine and new views will be added (as
part of IEP-35)
пт, 18 окт. 2019 г. в 00:50, Denis Magda :
> Anton, Maxim,
>
> Are we planning to release the views as part of 2.8? Don't see them listed
> in
Anton, Maxim,
Are we planning to release the views as part of 2.8? Don't see them listed
in the important features section:
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Themostimportantreleasetasks
-
Denis
On Wed, Feb 14, 2018 at 1:49 AM Anton Vinogradov
Vova,
Could you confirm https://issues.apache.org/jira/browse/IGNITE-7527 ready
to be merged?
On Wed, Feb 14, 2018 at 12:01 PM, Vladimir Ozerov
wrote:
> I would start with NODES and NODE_ATTRIBUTES as the most simple thing.
>
> On Tue, Feb 13, 2018 at 4:10 AM, Denis Magda wrote:
>
> > Alex P,
I would start with NODES and NODE_ATTRIBUTES as the most simple thing.
On Tue, Feb 13, 2018 at 4:10 AM, Denis Magda wrote:
> Alex P, sounds like a good plan for me.
>
> Vladimir, do you have any suggestions or corrections?
>
> —
> Denis
>
> > On Feb 12, 2018, at 4:57 AM, Alex Plehanov
> wrote:
Alex P, sounds like a good plan for me.
Vladimir, do you have any suggestions or corrections?
—
Denis
> On Feb 12, 2018, at 4:57 AM, Alex Plehanov wrote:
>
> The views engine and the first view are almost ready to merge (review
> comments are resolved). Which views should we take next? My prop
The views engine and the first view are almost ready to merge (review
comments are resolved). Which views should we take next? My proposal -
NODES, NODE_ATTRIBUTES, NODE_METRICS, NODE_HOSTS and NODE_ADDRESSES, since
these views are clear and all topology data available on each node.
Any objections?
Anton, Vladimir, I've made some fixes. There is only one view left and it's
renamed to 'IGNITE.LOCAL_TRANSACTIONS'.
High level design of solution:
When IgniteH2Indexing is starting, it create and start
new GridH2SysViewProcessor, which create and register in H2 (via its own
table engine) all imple
I've created IEP-13 [1] to cover all cases.
Feel free to create issues.
[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75962769
On Wed, Jan 24, 2018 at 6:10 PM, Vladimir Ozerov
wrote:
> Let's start with a single and the most simple view, e.g.
> LOCAL_TRANSACTIONS. We will
Let's start with a single and the most simple view, e.g.
LOCAL_TRANSACTIONS. We will review and merge it along with necessary
infrastructure. Then will handle the rest view in separate tickets and
separate focused discussions.
On Wed, Jan 24, 2018 at 5:29 PM, Alex Plehanov
wrote:
> 1) It’s not a
1) It’s not a principal point, I can change schema. The INFORMATION_SCHEMA
was used because it’s already exists and usually used for metadata tables
and views. Your proposal is to use schema “IGNITE”, am I understand you
right? BTW, for now, we can’t query another (H2) meta tables from the
INFORMAT
Hi Alex,
System views could be extremely valuable addition for Ignite. Ideally, user
should be able to monitor and manage state of the whole cluster with a
single SQL command line. We have plans to implement it for a very long
time. However, this is very sensitive task which should take a lot of
m
Hello, Igniters!
For Ignite diagnostic usually it’s helpful to get some Ignite internals
information. But currently, in my opinion, there are no convenient tools
for this purpose:
·Some issues can be solved by analyzing log files. Log files are
useful for dumps, but sometimes they are dif
16 matches
Mail list logo
