[megan_mcp]

Hi  !

The external component is using <iframe> to render external content so using “ip:port” is ok.
The problem is that CORS (cross origin resource sharing) policies have changed over time (more restrictive now than they used to be, because of security risks), so accessing other url(ip:port) than of the origin, requires extra http-headers configuration (probably on both sides: origin/iframe).

Hope this helps!

Thanks,

Megan

[megan_mcp]

Hi ,

When it says it will “avoid some checks and operations”  this is due to unix domain sockets (UDS ) avoiding things related to the tcp/ip stack (headers, routing, ) – the kdb+ code itself is the same for both. Tcp/ip loopback interface has gotten more efficient over the years, so its always worth benchmarking your particular use-case against both.
UDS buffers do not auto-tune, unlike tcp, and whilst setting the send buffer size can impact performance, setting the recv buffer has no impact – neither of these are settable from within kdb+ yet. This can impact performance where large data sets (that exceed the uds send buffer size) are being transferred between otherwise busy processes.

Hope this helps!

Thanks,

Megan

[megan_mcp]

Hi ,

To rename table columns you can use xcol cols, xcol, xcols | Reference | kdb+ and q documentation – Kdb+ and q documentation (kx.com)

Let me know if this works.

Thanks,

Megan

[megan_mcp]

Hi !

Have you had a look at our video on Querying Data using KX Dashboards? It includes a tutorial on how to create a view state. https://youtu.be/kTYSScDXDHc

If you still are unsure, let me know and I’ll go in to more detail.

Many thanks,

Megan

[megan_mcp]

Hi ,

We took a look at your instance and it was only a matter of reloading the database.

The values were overwritten when you manually ran the datacreation.q file.

It’s fixed now, good luck with the rest of the capstone!

Many thanks,

Megan

[megan_mcp]

Hi ,

The q files under FP.Setup should never be ran manually. These run automatically when you first load the capstone.

By running this file again manually it affects the integrity of the data within the tables.

What I suggest is downloading any answers to questions you’ve already passed so that we can wipe your instance and you can start again.

Hope this helps,

Megan

 

[megan_mcp]

Hi  !

We actually have a dedicated team that specialises in helping with KDB.AI questions – support@kdbai.com

Hope this helps!

Megan

[megan_mcp]

Hi  !

In order to execute across a handle, you must either use symbol or string execution.

So instead of having:

 

hdbH .perm.users

 

Try using the string method:

 

hdbH ".perm.users"

 

Let me know if this works!

Thanks,

Megan

 

[megan_mcp]

Hi ,

Can I ask you to send me your code for 3.1?

Thanks,

Megan

[megan_mcp]

Hi ,

My suggestion is to close down/restart all the tabs needed for this workshop and re-launch the sandbox.

If you are still experiencing this error, try opening it in a private browser.

Let me know if this works.

Many thanks,

Megan

[megan_mcp]

Hi ,

Can you send your code for these exercises using the spoiler tag?

Thanks,

Megan

[megan_mcp]

Hi ,

The issue is that you haven’t loaded the f1 database on port 5099,  which might explain why when you run the tests for 3.6, which includes testing that fiauser can run the function getSummaryReport[], you are getting a the sensor error as sensor does not exist on port 5099.

If you load in the f1 database, the error should be resolved.

Thanks,

Megan

[megan_mcp]

Hi ,

Can I just note that by converting your symbols to strings in col2, you are going to take up a lot more memory. If it isn’t essential they be stored in the table as strings, you could convert them while querying your data instead.

Of course this is only relevant if the table will be saved on disk and if you are interested in saving memory.

Thanks,

Megan

[megan_mcp]

Hi ,

I see you have sorted your trade table in ascending order by time and option_id, but as you can see by the sample data, the trade table isn’t sorted at all.

However, if we look at the nbbo table, you can see it is sorted in ascending order by time.

By sorting tables that do not require it and then preceding to join these tables together is where you can experience an overall table with an incorrect format.

Hope this helps,

Megan

[megan_mcp]

Hi ,

You appear to be upserting at a table level, you could try doing the upserts at a column level and peach it. something like:

{colData:get .Q.dd[`:kdbfolder_n/<date>/trade;x];upsert[.Q.dd[`:kdbcommon/<date>/trade/;x];colData]}peach except[cols trade;`date]

For this you need to have threads enabled in the command line:

-s N

Let me know if this works,

Megan