Skip to content

03-SML

Sml config
1. Update taos.cfg with sml related configurations
2. Restart taosd to make configurations take effect
3. Use sml_test tool to ingest sml data
4. Verify the data correctness after ingestion

InfluxDB line protocol
1. Basic InfluxDB line protocol parsing
2. Automatic table schema creation
3. Data type inference and conversion
4. Dynamic schema evolution support
5. Batch insertion functionality
6. Multi-threading concurrent insertion
7. Column and tag limit validation
8. String length boundary testing
9. Error handling and validation
10. Timestamp format compatibility

OpenTSDB json protocol
1. Basic OpenTSDB JSON protocol parsing
2. Automatic schema creation and evolution
3. Data type validation and conversion
4. Timestamp format compatibility testing
5. Multi-threading concurrent insertion safety
6. Table and column naming restrictions
7. Batch insertion functionality validation
8. String length and encoding boundaries
9. Error handling and exception management
10. Performance and memory usage optimization

OpenTSDB telnet protocol
1. Basic OpenTSDB Telnet protocol parsing
2. Automatic table schema creation and evolution
3. Data type validation with overflow detection
4. Multi-threading concurrent insertion safety
5. TCP telnet protocol network insertion
6. String length and encoding boundaries
7. Table naming restrictions and validation
8. Batch insertion performance testing
9. Error handling and exception management
10. Tag and column limit enforcement

Write sml restart
1. taosBenchmark sml data with json file
2. line_protocol include json/line/telnet
3. insert mode include: taosc/stmt
4. Restart taosd after writing over
5. Query server and client version
6. Verify taosBenchmark write sml data correct

Sml bugs TD-19291
1. Jira TD-19291: Support schemaless insert with super long tag value
2. Verify the data correctness after ingestion
3. Cleanup the test data

Sml bugs TS-3724
1. Jira TS-3724: Support schemaless insert with special characters in tag values
2. Verify the data correctness after ingestion
3. Cleanup the test data