stanford-futuredata / sparser Goto Github PK

An integration with the Flink SQL engine would be useful as well.

I would like to point out that identifiers like “_BITMAP_H_” and “_SPARSER_H_” do eventually not fit to the expected naming convention of the C language standard.
Would you like to adjust your selection for unique names?

Would you like to add more error handling for return values from functions like the following?

• calloc ⇒ bitmap_new
• sparser_new_query ⇒ sparser_calibrate

In table 3 of your excellent VLDB paper you have several queries, but left out the table names. I tried the demo using a pcap file with the query "select count(*) from dns" on a 1GB pcap file but it returned 0 rows. Is there a trick to know what the valid table names are for various input files that I am missing?

Hi! Is it possible to provide the link for the JSON file for demo?