Provide sqlite configs as cmdline flags#189
Conversation
Signed-off-by: Andrea Lamparelli <a.lamparelli95@gmail.com>
a9c3d39 to
ec5bb0a
Compare
|
Nit: you might want to update this comment: https://github.com/google/ml-metadata/pull/189/files#diff-0c3fe2859affc74bb85407ef9414003f0f77e4d5a0db30d3f67e57b03c5979ebR344 Edit: this error message must also be updated: https://github.com/google/ml-metadata/pull/189/files#diff-0c3fe2859affc74bb85407ef9414003f0f77e4d5a0db30d3f67e57b03c5979ebR340 |
Co-authored-by: Isabella Basso <isabellabdoamaral@gmail.com>
Nice catch, updated! |
|
Hey @XinranTang, is there any chance to get this in? |
Any news? |
While using
ml-metadataI noticed that there is no way to startup the server usingsqliteconfiguration through flags, the only way I found (as stated by the documentation) was to use theconfig_filefile option pointing to apbfile like:connection_config { sqlite { filename_uri: '/tmp/test_db' connection_mode: READWRITE_OPENCREATE } }With this pull request I am proposing to introduce the possibility to startup the grpc server with
sqliteconfig using cmdline flags, similarly to what is currently supported formysqlandpostgresql.Given this, the previous configuration could be replaced by cmdline flags as follow:
Technical addition
This PR proposes to add a:
metadata_source_config_typenamedsqlitemetadata_source_config_type==sqlite:--sqlite_config_filename_uri: required, specifies the sqlite db uri.--sqlite_config_connection_mode: optional, specifies the sqlite connection mode. Default isREADWRITE_OPENCREATE