error retriveing tree

Community Support
1

The connected server does not show the tables name.

\v . does.

The pic of the problem is attached.

2

Interesting. Would you mind terribly to try if qPad (qinsightpad.com) is capable of retrieving tree of that instance or not?

Thanks in advance,

Oleg

3

This is a qStudio-specific issue, not a kdb issue, so you should in future reach out to timestored.com for official technical support. 

The issue is that the specific command (pasted below) to build the server tree has encountered an error and thus couldn’t display the server tree. I’ve seen this happen before in cases where a table was removed from a hdb (historical table removals aren’t handled so well since the tables still “appear” to be there). In that case the instance needs to be restarted and that generally fixes the server tree issue. 

Either way, here is the code snipped then generates the tree. You could debug it to see exactly where it fails

{   nsl:“.”,/:string ,key ;

      nsf:{[ns]       

            ff:{[viewset; v; fullname; sname]    

                  findColArgs:{$[.Q.qt x; cols x; 100h~type x; (value x)1]};         

                  safeCount: {$[.Q.qp x; $[pn in key .Q; {$[count x;sum x;-1]} .Q.pn y; -1]; count x]};

                  (type v; safeCount[v;fullname]; .Q.qt v; .Q.qp v; findColArgs v; sname in viewset)};   

            vws: system "b ",ns;

            n: asc key[$ns] except ;       

            fn: $[ns~enlist “.”; n; ns,/:“.”,/:string n];

            n!.'[ff[vws;;;];flip (@[`$ns; n]; fn; n)]};   

      (`$nsl)!nsf each nsl}

Terry

4

Yes, it is.

? 2018?12?4??? UTC+8??12:50:28?_Oz_???

Interesting. Would you mind terribly to try if qPad (qinsightpad.com) is capable of retrieving tree of that instance or not?

Thanks in advance,

Oleg

5

Thanks for the detailed explanation.

I am new to kdb+, but findColArgs seems problematic. 

After debugging, it works fine, only the tree is still not showing.

Cheers,

Sly

? 2018?12?4??? UTC+8??6:19:05?TerryLynch???

This is a qStudio-specific issue, not a kdb issue, so you should in future reach out to timestored.com for official technical support. 

The issue is that the specific command (pasted below) to build the server tree has encountered an error and thus couldn’t display the server tree. I’ve seen this happen before in cases where a table was removed from a hdb (historical table removals aren’t handled so well since the tables still “appear” to be there). In that case the instance needs to be restarted and that generally fixes the server tree issue. 

Either way, here is the code snipped then generates the tree. You could debug it to see exactly where it fails

{   nsl:“.”,/:string ,key ;

      nsf:{[ns]       

            ff:{[viewset; v; fullname; sname]    

                  findColArgs:{$[.Q.qt x; cols x; 100h~type x; (value x)1]};         

                  safeCount: {$[.Q.qp x; $[pn in key .Q; {$[count x;sum x;-1]} .Q.pn y; -1]; count x]};

                  (type v; safeCount[v;fullname]; .Q.qt v; .Q.qp v; findColArgs v; sname in viewset)};   

            vws: system "b ",ns;

            n: asc key[$ns] except ;       

            fn: $[ns~enlist “.”; n; ns,/:“.”,/:string n];

            n!.'[ff[vws;;;];flip (@[`$ns; n]; fn; n)]};   

      (`$nsl)!nsf each nsl}

Terry