A new table has been added to the KDB Ticker for new functionality in
the system. However, HDB cannot know information about the new table
unless RDB saves memory data as an End of Day file.Is there a good way?
I understand that kdb-tick should be run in order from ticker. However,
if ticker is terminated for some reason, rdb does not subscribe to the
re-run ticker. Need a way to re-subscribe or a reference for
implementation.
Docker image-based container environment has been widely used. However,
the Docker Compose for KDB-TICK is not found. Can I get some documents
for reference? The image of Docker Hub is mostly 32bit. The 32-bit
version is no longer available. Do I hav...
I'm use KxSystems/javakdb with commons-pool2. Is the connection pool
meaningless because KDB+ is a single thread? Is it better to connect a
TCP session when a request is required? Is there any advantage in using
Flip in Java rather than .j.j when pro...
We purchased a 2-core license. Is there no host limit per license? if
when I configure the tick system with multiple servers, I would like to
know if I can use it as one license.
@rocuinneagain wrote: There are some notes on late data in this blog
post: https://kx.com/blog/partitioning-data-in-kdb/ It outlines the
basics of using lookup tables per partition. Another option involves
taking copies of HDB partitions and upsertin...
If you have a lot of days to save and it takes a lot of time, is the
only way to increase disk performance?. I recognize that it does not fit
the KDB TICK concept that a lot of past data is registered at the
current time. Thank you.
