Hello, anyone know how to change localCSV route to...
# feedback-and-requests
a
Hello, anyone know how to change localCSV route to GoogleDrive route? Thanks🙂
u
Hey @Ander del Valle Castaños, while we don't have official docs for this (yet), this issue (and the linked slack chat) might help you 😄
u
thanks @George Claireaux (Airbyte), in these case the SourceType, is Google Directory?
a
The above just uses the standard files source. A dedicated Google Drive connector doesn't exist (yet)
u
Well, i will try to connect with this?
u
Yes if you use HTTPS as the provider and then your url should look something like:
<https://drive.google.com/uc?export=download&id=><DRIVE_FILE_ID>
where
<DRIVE_FILE_ID>
will be unique to your specific file.
u
But this option is not possible as Destination-File, is correct?
u
only is possible as SourceFile
u
ah you want to use google drive as destination? I don't believe there is any way to do that currently... however you could create an issue for it to get it in our backlog 😄
u
Okey, thanks
a
I have requested the connector
u
But there are a LocalCSV connector for destination
u
is possible to configure http-URL with this option?
u
Because, i have tested this connector and it creates the files in my local Docker Image TMP-url
u
Maybe, is possible to change configuration to redirect the path to HTTP
u
I suppose technically if you could mount your google drive to the container, then modify LOCAL_ROOT to point there (see local_csv docs) you might be able to make this work
u
u
Thanks @George Claireaux (Airbyte), can you know how to change LOCAL_ROOT of destination files?
u
i try to read the guide but i dont find the parameters
u
it's an environment variable set in the .env file. However you could get around changing that by doing something like:
u
But you'd need to make sure you mount your google drive to "/tmp/airbyte_local/cars/models" where
/cars/models
in this example you replace with whatever you want
u
thanks @George Claireaux (Airbyte)
s
the process of mount drive i think have the limit of need access to local computer
u
lmk how it goes 😄
u
is possible to create a connector HTTP?
u
it can be a custom connector, because it not appear on list of standard
u
yeah the ideal solution here would be building a google drive connector (using our CDK) and the google drive API
u
yes, it is for drive
s
but is possible to create more generic
u
as Source File Connector?
u
do you think?
u
i think the best option is replicate it
u
do you mean a generic destination file connector?
u
We effectively have a base for this with the S3 destination as it provides functionality for writing into various file formats so this could be reused to build a google drive connector
u
I think generally the more generic a connector, the more full of if/else or case statements the code is, and the less reliable it is across all cases. The better approach is to build abstract layers that hold the reusable elements and then implement specific connectors building on top of those
u
OK, thanks i will try replicate S3 destination connector
s
for deploy connector after creation , i can do that directly?
u
p
this tutorial allows to create source and Destination connectors?
u
i read using CDK is easy to create part of connector
u
^ that's specifically for sources
u
^ if you're more comfortable with python then use that, I just linked the java one because the file handling code already exists in the s3 destination and is in java
u
yes, it is okey
p
i think that this is the code for replicate with Drive, that you refer