[skywalking-query-protocol] branch feature/log-debug updated (2cd5bb2 -> f725c38)

[ke...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

kezhenxu94 pushed a change to branch feature/log-debug
in repository https://gitbox.apache.org/repos/asf/skywalking-query-protocol.git.


 discard 2cd5bb2  Add an API for LAL debug
     new f725c38  Add an API for LAL debug

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (2cd5bb2)
            \
             N -- N -- N   refs/heads/feature/log-debug (f725c38)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 log.graphqls | 1 +
 1 file changed, 1 insertion(+)

[skywalking-query-protocol] 01/01: Add an API for LAL debug

[ke...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

kezhenxu94 pushed a commit to branch feature/log-debug
in repository https://gitbox.apache.org/repos/asf/skywalking-query-protocol.git

commit f725c3822de13ebf2d2c2d26f7e41b9f20382777
Author: kezhenxu94 <ke...@apache.org>
AuthorDate: Tue Aug 17 20:02:20 2021 +0800

    Add an API for LAL debug
---
 log.graphqls | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/log.graphqls b/log.graphqls
index f5b126f..6b9900a 100644
--- a/log.graphqls
+++ b/log.graphqls
@@ -79,4 +79,8 @@ extend type Query {
     # Return true if the current storage implementation supports fuzzy query for logs.
     supportQueryLogsByKeywords: Boolean!
     queryLogs(condition: LogQueryCondition): Logs
+
+    # Test the logs and get the results of the LAL output.
+    # The results are guaranteed to be in JSON format.
+    test(log: [String!]): [String!]
 }