Releases: DataIntellectTech/TorQ
Releases · DataIntellectTech/TorQ
Bug fix for Chained TP
Patch release to bug fix the chained TP to allow it to start up correctly when a specific subscription list of tables is supplied
Initial release of TorQ 2.5
- Added u.q - publish/subscribe code from KDB+ Tick
- Improved memusage.q to do sampling
- Updated dataloader.q
- Make sure all config can be read from KDBAPPCONFIG
Initial release of TorQ 2.4
- Added k4unit to allow tests to be automatically run via the -test parameter
- Extended application config handling so all default config can be found in $KDBAPPCONFIG
- Bug Fixes
Initial Release of TorQ 2.3
- Added optional write down method to wdb process, which allows data to be written to custom partition schemes during the day. At the end of day before being moved to the hdb, data is merged instead of sorted, which will allow the data to be accessed sooner. The optional method may present a significant saving in time for datasets with a low cardinality (small distinct number of elements), i.e. FX market data
- Added write access control to message handlers (using reval), which restricts the ability of querying clients to modify data in place
- Added functionality to return approximate memory size of kdb+ objects
- Bug fixes
Release of TorQ 2.2.1
- Bug fix - fixed endofdaysort to not throw type error when par.txt is available
- Bug fix - fixed gateway so results are not dropped when a client loses connection and another is querying multiple servers
Initial Release of TorQ 2.2
- Added application configuration management using $KDBAPPCONFIG environment variable
- Added pid, host and port to heartbeat table
- Changed gateway to be non intrusive
- Bug fixes
Initial Release of TorQ 2.1
- Added a chained tickerplant process
- Updated housekeeping.csv to take in an extra column agemin which represents whether to use minutes or days in find function
- Updated email libraries
Initial release of TorQ 2.0
- Added RDB process which extends r.q from kdb+ tick.
- Added WDB to write down data periodically throughout the day. Extends w.q.
RDB and WDB allow seamless end-of-day event (no data outage, no tickerplant back pressure) - Added Reporting Process to run reports periodically and process the results
- Added environment variable resolution to process.csv to allow greater portability. If a process is started without a port specified it will look it up from process.csv based on the proctype and procname.
- Added -localtime flag to allow process to run in localtime rather than GMT (log message, timer calls etc.). The change is backwardly compatible - without -localtime flag the process will print logs etc. in GMT but can also have a different .z.P
- Added Subscription code to manage multiple subscriptions to different data sources
- Added email library which uses libcurl. Used to send emails from TorQ processes
- Added standard monitoring checks to the database code
- Added data loader script. Utility functions to load a directory of data into a database in chunks, sort and part at the end
- Added tickerplant log recovery utilities to recover as many messages as possible from a log file rather than just stopping at the first bad message
- Added compression process to run and compress a given database
- Modified compression code to handle par.txt databases
- Modified compression code and housekeeping process to run with kdb+ 2.*
- Modified std out/err logging and usage logging to include process name and process type (the logmsg table had changed along with some of the functions in the .lg namespace so you might need to check in case you have overridden any of them)
- Removed launchtick scripts and some default configuration: to create a test system, install a starter pack
Initial Github Release : codebase from code.kx.com
This is an initial release with the code base copied from code.kx.com