Fetch hk#771
Conversation
|
@jlashner could you take a look at this? |
|
Suggestions:
I know this is answering a need for a faster way to do something. Loading HK in a single pass is going to be the fastest. But I think someone should take a high-level look at the HK problem... I am concerned that we are getting new ways of loading HK all the time, without necessarily converging on a single better way. |
|
Did we decide whether this tool is still valuable? |
|
I know this is something we've discussed before, but looking at the code now I'm left a little confused as to what the use case is. Namely, how do users know what g3 files they need to be scanning? Are there other functions in hk_util that give you the files to scan for a given time range and is this addressing a particular inefficiency in load_range? I think since we're on the verge of getting hkdb instances running, I think if we can't think of clear use cases, I'm tempted to say we close this to avoid adding more confusion as to which hk loading function does what. |
|
I agree--I was pruning my old branches and draft PR's and when coming across this one, I couldn't justify a use case for this. |
This is a working version for speeding up hk loading using .g3 frames.
Args are
pathto HK .g3 filename and a list offields. IffieldsisNone, data for all fields in that .g3 file are returned. Skips any address in .g3 frames that hasdaq-registryin it.