SQLite as a Result File Format in OMNeT++ OMNeT++ Community Summit 2016, Brno University of Technology (FIT-BUT), Sept 15-16. Rudolf Hornig OMNeT++ Result Files ● Scalar and Vector files ● Contents: Contents: ○ Run description ○ Scalar file: (module, scalar, value), histograms, result attributes ○ Vector file: vector data: (module, vectorname, vector data = (timestamp+value)*) ● Current format: ○ utVectorManager" 7 Using SQLite Result Files from OMNeT++ IDE SQLite Result Files can be used from the IDE just like the text based format. 8 Using SQLite Result Files Directly There are several

tbl1 tbl1 limit limit 10 10 into into outfile outfile "file:///home/work/path/result_" "file:///home/work/path/result_";; ++------------+-----------+----------+--------------+ ------------+-------- bos://my_bucket/result_ bos://my_bucket/result_ my_broker my_broker ,, \n \n SELECT SELECT ** FROM FROM tbl tbl INTO INTO OUTFILE OUTFILE "bos://my_bucket/result_" "bos://my_bucket/result_" FORMAT "max_file_size" == "100MB" "100MB" ));; result_0.csv result_0.csv result_0.csv, result_1.csv, ... result_0.csv, result_1.csv, ... bos://my_bucket/result_ bos://my_bucket/result_ WITH WITH x1 x1 AS AS ((SELECT

plan that collects input from multiple sources and merges the results to produce the correct query result. Evaluation Model An execution plan consists of operators, each of which implements a specific piece data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent key-value store Key already exists (/vitess/global) [6] MySQL Fails to Initialize This error is most likely the result of SELinux enabled: 1027 18:28:23.462926 19486 mysqld.go:734] mysqld --initialize -insecure failed:

plan that collects input from multiple sources and merges the results to produce the correct query result. Evaluation Model An execution plan consists of operators, each of which implements a specific piece join the incoming results into a single result that the user receives. The queries that MySQL gets are often just pieces of the original query, and the final result will get assembled at the vtgate level whatever it already is. • Not supported. For these settings, attempting to change them will always result in an error. • Vitess aware. These are settings that change Vitess’ behaviour, and are not sent down

plan that collects input from multiple sources and merges the results to produce the correct query result. Evaluation Model An execution plan consists of operators, each of which implements a specific piece join the incoming results into a single result that the user receives. The queries that MySQL gets are often just pieces of the original query, and the final result will get assembled at the vtgate level whatever it already is. • Not supported. For these settings, attempting to change them will always result in an error. • Vitess aware. These are settings that change Vitess’ behaviour, and are not sent down

plan that collects input from multiple sources and merges the results to produce the correct query result. 20 Evaluation Model An execution plan consists of operators, each of which implements a specific join the incoming results into a single result that the user receives. The queries that MySQL gets are often just pieces of the original query, and the final result will get assembled at the vtgate level whatever it already is. • Not supported. For these settings, attempting to change them will always result in an error. • Vitess aware. These are settings that change Vitess’ behaviour, and are not sent down

plan that collects input from multiple sources and merges the results to produce the correct query result. Evaluation Model An execution plan consists of operators, each of which implements a specific piece join the incoming results into a single result that the user receives. The queries that MySQL gets are often just pieces of the original query, and the final result will get assembled at the vtgate level whatever it already is. • Not supported. For these settings, attempting to change them will always result in an error. • Vitess aware. These are settings that change Vitess’ behaviour, and are not sent down

.............689 31.3.2. Retrieving Query Result Information .............................................................696 31.3.3. Retrieving Other Result Information .............................. .....................................................782 33.5.1. Executing Statements without a Result Set ....................................................782 33.5.2. Executing a Statement with Input Parameters ................................................782 33.5.3. Executing a Statement with a Result Set ........................................................783 33.6. pgtypes Library..........

.................652 31.3.2. Retrieving Query Result Information ......................................................659 31.3.3. Retrieving Other Result Information ................................. .....................................................739 33.5.1. Executing Statements without a Result Set .............................................739 33.5.2. Executing a Statement with Input Parameters Parameters .........................................740 33.5.3. Executing a Statement with a Result Set .................................................740 33.6. pgtypes Library.......................

plan that collects input from multiple sources and merges the results to produce the correct query result. Evaluation Model An execution plan consists of operators, each of which implements a specific piece join the incoming results into a single result that the user receives. The queries that MySQL gets are often just pieces of the original query, and the final result will get assembled at the vtgate level whatever it already is. • Not supported. For these settings, attempting to change them will always result in an error. • Vitess aware. These are settings that change Vitess’ behaviour, and are not sent down