[davidcrossey]

Very nice  !
Just to make your solution visually easier to read, I’ve casted to symbols:

q)progression:`$("C";"C#";"D";"D#";"E";"F";"F#";"G";"G#";"A";"A#";"B") 
q)notes:flip progression mod[;12]til[13]+/:progression? 
q)notes `$'"EADGBE" 
E A D G B E F A# D# G# C F F# B E A C# F# G C F A# D G G# C# F# B D# G# A D G C E A A# D# G# C# F A# B E A D F# B C F A# D# G C C# F# B E G# C# D G C F A D D# G# C# F# A# D# E A D G B E

And to satisfy  for a one-liner, condensed as:

{flip x mod[;12]til[13]+/:x?y}[`$(“C”;”C#”;”D”;”D#”;”E”;”F”;”F#”;”G”;”G#”;”A”;”A#”;”B”);`$'”EADGBE”]

Look forward to seeing how others approach this problem.

[davidcrossey]

Hi erichards,

You could partition by int in this case – note, a sym is just a mapping to an integer value anyway, so you could use that for your partitioning. A blog from Aqua-Q here that discusses how this is applicable to IoT, and how you may manage the mapping as an example: kdb+ IoT Database Structure | AquaQ

In terms of upper limit, I presume that would be the max integer value, but my best advice would be to mock up a database with some int partitions to see how performant it is and any limitations that come with it for your use-case.

One consideration to keep in mind is that depending on your data read/write access patterns, some partitions could grow exponentially large, in which case you may want to add another layer of abstraction to your write down – e.g. int = year+sym for better query distribution later.

Hope this helps.

[davidcrossey]

Hi trosales,

You could write a callback function to gather more information from your q process and return the result, or perhaps consider extending the .z functionality, for example see Using modified .z functions to trace, monitor and control execution Knowledge Base kdb+ and q documentation – Kdb+ and q documentation (kx.com)

 

[davidcrossey]

Hi Simon,

You can leave the type of the (future) string column as empty in the table definition and let q infer the type once the first upsert occurs:

 

q)test: ([]test: `$(); uptar:()); 
q)test upsert ([]test: `rta; uptar: enlist "ra") 
test uptar 
---------- 
rta "ra" 

q)meta test upsert ([]test: `rta; uptar: enlist "ra") 
c    | t f a 
-----| ----- 
test | s 
uptar| C

 

Happy Christmas!

[davidcrossey]

Hi mchlma256,

Please refer to Licensing kdb+ Learn kdb+ and q documentation – Kdb+ and q documentation (kx.com)

Regards,

[davidcrossey]

Perhaps the answer is in your question; if a q process is not actively executing e.g. a script, listening on a port to process some work or connected to stdin (interactive mode), then what is it’s purpose?

From the perspective of the process, there is nothing left to do and thus doesn’t need to be running. That would be my guess as to why this is the default behavior built into the binary.

Perhaps someone closer to core implementation will be able to share more insight.

[davidcrossey]

Hi leguan,

If you check INSTANCE_CONFIG:default in KX Control you should be able to see the default settings as per Enhanced instance configuration – KX Platform

If you want to disable the logging of async queries, you can disable .pm.async.logEnabled

Hope this helps

[davidcrossey]

I’d go with the dummy port versus wasting CPU cycles checking

[davidcrossey]

Hi Vinor_Sarder,

You should be able to simply toggle the field visible by linking the viewstates as you’ve mentioned above.

If that’s not working, you could create e.g. a button which triggers a data source (via run-query ) that inspects the current value of IsColumn1Hidden, negates it and maps that value back to IsColumn1Hidden

[davidcrossey]

Hi Vinod_Sardar,

It depends on the product. Are you using KX Platform + Dashboards, or Dashboards Direct?

If it’s the prior, the viewstate settings can be viewed in KX Control UI through the navigation tree. Search for the dashboard GUID and you’ll see it with the username appended on the end.

If in Dashboards Direct, if I recall correctly, you can either find these under the installation directory in the /data folder or within your browser session cookies.

Hope this helps your search, let us know your findings

[davidcrossey]

Potentially, in which case you’d need to work with the options as per your link, along with your Systems Administrator.

Alternatively, you could try to install it yourself (assuming you can download the relevant packages to your machine)

See here: Set up your machine-learning environment Machine Learning kdb+ and q documentation – Kdb+ and q documentation (kx.com)

 

[davidcrossey]

Hi jk311,

Did you retry per the last message?

I only ask as I’ve just ran the same on my Windows machine and it’s connecting to the repo as expected:

 

Regards,

David

[davidcrossey]

Hi cj,

You should only need to re-import your separate package if you do an upgrade of Platform.

If you are simply restarting the system, that shouldn’t impact the current version of entities across the application.

To make sure, you can run a test by stopping and restarting the application and reviewing the state.

Hope this helps,

David

[davidcrossey]

Hi k-mambo,

Yes, the host is typically restricted for commerical licences.

You can quickly find this out if you attempt to run q with the licence file not permitted for that host:

‘host

See here for more.

I would also suggest contacting your internal procurement team to find out more on the your specific licence restrictions.

Kind regards,

David

[davidcrossey]

I don’t think it’s related to having Developer in the same folder (although I would suggest having it in its own location).

You perhaps may be missing some libraries that are required for authentication based on the log messages.

Can you try changing authentication to disabled in your config.bat and see if you can start Developer?