You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Source code mentions -p to be deprecated over --catalog, however replacing -p by --catalog leads to different behaviour: the "selected": true on a schema definition in the catalog file is not honoured by --catalog, but is by -p parameter.
It would be helpful if this could be clarified a bit more in the docs.
The text was updated successfully, but these errors were encountered:
Thanks for the feedback, @ChrisCalculus. As you noted, the -p- is deprecated in favor of using the --catalog. We're shifting towards usage of metadata in the catalog for noting which fields should be selected. We agree that the documentation needs some work and plan to address that in the future. We'll update here when that happens.
It might be me, but the use of the --catalog and property -p parameters is somewhat unclear to me.
They are used intermixed throughout different sections of the docs (e.g. Allowing Users to Select Streams to Sync vs. Sync mode).
Source code mentions -p to be deprecated over --catalog, however replacing -p by --catalog leads to different behaviour: the
"selected": true
on a schema definition in the catalog file is not honoured by --catalog, but is by -p parameter.It would be helpful if this could be clarified a bit more in the docs.
The text was updated successfully, but these errors were encountered: