-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
connector:issue requires long --database and --table arguments #67
Comments
I vote for that too. I wondered about the same yesterday. |
Sounds good. As another suggestion, I think that it's better that users can declare configuration file for connector:issue.
Key points:
|
@muga Thanks, in: and out: should be handled by #73 'td connector:issue config db table' is easy to implement like the following. But I'm unsure it's needed now because we can't remove --database and --table already.
|
Using config file would be the best idea as @muga describes. Because config file can be consistent with embulk-output-td, which makes it easy to migrate between TD data connector and local embulk. However, setting database and table names in |
For example, current
The suggestion on this ticket is following:
|
but other commands like bulk_import or import uses just
<db> <table>
arguments. Can't we use this way instead?The text was updated successfully, but these errors were encountered: