Hi,I am trying to load splayed table (historical db) that used to workjust fine. Now if I am attempting to load it (\l /path/to/table) itshows this:k){$[0>@!x:-1!x;. x;x`]}`type.:`:-laI am trying to trace back recent changes, but I am a bit lost. Cansomeone help me understand the k error message?
Is there any way to diagnose this type of problems? See moredescriptive error message?On Dec 8, 8:52?am, Georgy Bolyuba <boly…> wrote:> ? Hi,>> I am trying to load splayed table (historical db) that used to work> just fine. Now if I am attempting to load it (\l /path/to/table) it> shows this:>> k){$[0>@!x:-1!x;. x;x`]}> `type> .:> `:-la>> I am trying to trace back recent changes, but I am a bit lost. Can> someone help me understand the k error message?</boly…>
it is trying to load file
-la
which is not of a kdb+ binary type.
Presumably you have a file called “-la” somewhere within your hdb filesystem.
That was it. Thank you!Another quick question: is there a way to tell KDB that splayed tablechanged without bouncing it?On Thu, Dec 8, 2011 at 10:51 AM, Charles Skelton wrote:> it is trying to load file>> -la>> which is not of a kdb+ binary type.>> Presumably you have a file called “-la” somewhere within your hdb> filesystem.>> On Thu, Dec 8, 2011 at 8:52 AM, Georgy Bolyuba wrote:>>>> Hi,>>>> I am trying to load splayed table (historical db) that used to work>> just fine. Now if I am attempting to load it (\l /path/to/table) it>> shows this:>>>> k){$[0>@!x:-1!x;. x;x`]}>> `type>> .:>> `:-la>>>> I am trying to trace back recent changes, but I am a bit lost. Can>> someone help me understand the k error message?>> –>
Submitted via Google Groups
in an hdb, rescan for new partitions using
\l .
splays defer reading until used, so if they were present at original loading time, and changed since then, the changes should appear anyway without explicit reload/rescan.
Note that changing files in use by another kdb+ process may result in that process crashing.
Great, thank you!