[leahs]

I looked into this and discovered that the purpose of this file is to enable the PDF button on Dashboards.

The supporting documentation can be located here: https://code.kx.com/dashboards/publish/#pdf-server

Hope this helps!

Kind regards,

Leah

[leahs]

Super @leades

Confirming that this is the accepted solution when creating a highlight rule from a multiselect dropdown list.

Happy Coding ,

Leah

[leahs]

Hello,

Great content here! Thank you for sharing with the community

Looking forward to what fellow members will contribute.

Kind regards,

Leah

[leahs]

Reverting with feedback from our internal licensing admin experts:

“The endpoint is one of the following domains:

*kdbod.com

*kdbod.net

*kdbod.org

Only HTTP (port 80/tcp) is needed to these domains, there are no fixed IPs – though we front the service with more than one CDN provider – their IPs vary both depending on where you use the service and from one moment to the next.

It is recommended the user use a HTTP proxy server if they wish to enforce such restrictions, kdb+/q does honour the http_proxy environment variable. ”

We hope this helps you.

Kind regards,

Leah

[leahs]

Hello Simon,

I’m reverting with feedback shared by our internal pros. Kudos to Benjamin Jeffery here!

There appears to be two identifiable issues:

1. Analyst was not designed to work with .z.pd. As these secondary processes don’t have internal Analyst functions or other state defined, behaviour when using .z.pd is undefined. This limitation will be added to the documentation for the next Analyst release.

2. The handle to the secondary process is closing whenever peach is called with a locked function. An internal ticket has been raised acknowledging this.

Hope this helps. Thanks again for sharing with the community

Kind regards,

Leah

[leahs]

Hello @darrenwsun

Thank you for sharing this with the community!

The error generated is documented here: KX Licensing – Licensing server for kdb+ On Demand.

 

This implies that it requires a kc.lic license key file and an always-on internet connection to operate.

Perhaps you are encountering a firewall because you are connected to a corporate WI-FI or VPN? If so, maybe try this when not connected to the VPN.

However, if a constant internet connection is an issue, it is worth noting that 32-bit kdb+ does not have this requirement and would be the suggested workaround.

Kind regards,

Leah

 

[leahs]

 

Thank you for reverting with your progress update, Ori! Very helpful for fellow community members.

We’re working on feedback for your remaining question and we will share it as soon as possible.

Kind regards,

Leah

[leahs]

Thanks @matt_moore

The particular situation we encountered related to the client connecting to the RDB by opening an Analyst session and mounted the HDB. Despite the data being on disk, the sym file was loaded into memory and this was quite large. Other assigned variables were also kept in memory. It was this manual one time action that resulted in the RDB being busy for a length amount of time rather than having a persistent slow subscriber issue. This lead to the build up of data in the TP’s outbound buffer. We availed of .Q.w[] and .Q.gc[] while in the RDB process.

This prompted an internal investigation into memory limits of an Analyst session. The status of this is WIP.

Thanks,

Leah

[leahs]

Hello,

qpython is not a library that we own or support within FD/KX. Our library is EmbedPy or PyKDB.

Therefore, the error you’re encountering is not known by KX.

Perhaps a fellow contributor here on the community will have some knowledge to share with us.

Kind regards,

Leah

 

[leahs]

Coincidentally, we encountered an issue this week where the RDB being too busy negatively impacted the TP and caused a data build up in the TP’s outbound buffer.

For best practise, you can monitor the memory usage of subscribers by running .Q.w[] and memory stats in readable form will be returned – https://code.kx.com/q/ref/dotq/#qw-memory-stats

.Q.gc[] is also very important and can help with in-memory capacity issues.  https://code.kx.com/q/ref/dotq/#qgc-garbage-collect 

Thanks for sharing with the community. Hope this helps.

 

[leahs]

Great question! Here is the feedback I received when I investigated this internally:

“If broker is installed in a container, and client is on the host , then it should be possible to communicate as long as the chosen port is exposed to a port on the host.

If using solace broker container, they are normally listed in solace PubSubStandard_singleNode.yml.

Note: these are Solace queries rather than KX queries, and may be better directed to Solace for a better explanation, and it can be beneficial to try with the solace client examples first (directing any problems/queries/etc to Solace). The KX interface uses the same solace C APIs.”

Kind regards,

Leah

[leahs]

Hello Ori,

Great content here!

I’m going to link some helpful resources for you:

Solace interface to kdb+

and

Solace Installation

Hope this helps.

Kind regards,

Leah

[leahs]

Hello @ekallivrousis ,

Here are some great resources to help you on your q-bie journey:

Kdb+ and q documentation inspired by the best-known textbook for q, Q for Mortals

I usually tend to keep a tab open for the Reference Card too – great for learning!

Reference card

We also have a KX Training Academy offering courses and you can learn all about that here: KX Academy

This platform, the KX Community, is a great resource to engage with other q-bies or ‘the q gods’ will be more than happy to help you learn all things kdb+/q

Hope this helps. Best of Luck.

Leah

[leahs]

Hello again,

I followed up with an internal KX team and I will also share their feedback here:

Extra resources:

A whitepaper here: https://code.kx.com/q/wp/solace/

Examples here once installed: https://github.com/KxSystems/solace/tree/master/examples

Note: It is true that a solace broker is required. Solace messaging can not be run without a solace broker.

Tip: It is useful to start with the solace c examples and solace software to check that the solace setup including pub/sub/etc is working correctly.

Broker: https://solace.com/try-it-now/

C API (client pub/sub examples included): https://solace.com/downloads/

Some changes to the code.kx docs, https://code.kx.com/q/interfaces/solace/, are currently in the works. These specificities are mentioned in the readme/etc on github.

https://github.com/KxSystems/docs/pull/52

https://github.com/KxSystems/docs/pull/51

Hope this is helpful for you.

Kind regards,

Leah

[leahs]

Hello,

Thanks for sharing this with the community. Great content!

I believe the error generated is a result of your method for retrieving the unique OptionIDs. Given your table is partitioned, this method of taking columns from tables will not work . Hence the ‘unable to operate on a partitioned table’ error.

I suggest querying the table, meaning avail of Functional qSQL Statements as an alternate approach to obtain the unique OptionIDs from the trade table.

Functional qSQL information can be studied here: https://code.kx.com/q/basics/funsql/

Specifically focus your attention on the functional form ‘exec’  https://code.kx.com/q/ref/exec/

In summary, rather than

 

uniqueOpts:distinct trade`option_id

Create uniqueOpts by following the syntax below (provided in the previous link) where square brackets mark optional elements. This is what we refer to as ‘querying’ the table.

 

exec [distinct] ps [by pb] from texp [where pw]

 

The above code is a ‘hint’ and requires modification.

Hope this helps.

Kind regards,

Leah