-
Notifications
You must be signed in to change notification settings - Fork 40
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
Support for s3 compatible object storage #750
Comments
Thanks for creating the issue. cc @utkarsharma2 |
I'm seeing different results with below code:
Output:
for me AstroSDK is picking the right URL since I don't have MINIO on my local, failing to connect to it. Are you sure |
Interesting. I am pretty sure that connection is created using env since there are non-astro sdk dags which are running fine. But i will double check with your code. Between which astro sdk version did you used to test ? |
@mohittalele Can you try above dag and see if it works for you? I was using version - 1.0.2 |
@utkarsharma2 |
@utkarsharma2 were you able to reproduce it ? |
@mohittalele I'm still seeing the same results on local. Can you try to create a separate instance with the new airflow home dir and run the above-listed dag? |
@fletchjeff was trying it with minio and he had some issues too: https://astronomer.slack.com/archives/C02B8SPT93K/p1666289425280609 |
I think the issue here is that the This works for me running minio locally with a normal python session: from smart_open import open
import os, boto3
client = boto3.client('s3',
endpoint_url='http://localhost:9000/',
aws_access_key_id='minioadmin',
aws_secret_access_key='minioadmin',
)
for line in open("s3://test/smaller.csv",transport_params={'client': client}):
print(line) The with smart_open.open(self.path, mode="wb", transport_params=self.location.transport_params) as stream: I dont' think that |
# Description ## What is the current behavior? Currently, we were not able to connect to minio(https://min.io/) as a replacement for S3. Impact: load_file(), export_file() and minio as custom xcom backend related: #750 and slack thread - https://astronomer.slack.com/archives/C02B8SPT93K/p1666289425280609 ## What is the new behavior? Now we are passing all the required parameters to open_smart() to be able to communicate to minio server. ## Does this introduce a breaking change? Nope Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
@mohittalele this PR resolves the issue. Please check on your side. |
# Description ## What is the current behavior? Currently, we were not able to connect to minio(https://min.io/) as a replacement for S3. Impact: load_file(), export_file() and minio as custom xcom backend related: #750 and slack thread - https://astronomer.slack.com/archives/C02B8SPT93K/p1666289425280609 ## What is the new behavior? Now we are passing all the required parameters to open_smart() to be able to communicate to minio server. ## Does this introduce a breaking change? Nope Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
Describe the bug
I am trying to use the astr sdk with airflow 2.3.3, postgresql as database and minio as an s3 compatible object storage
Version
To Reproduce
Steps to reproduce the behavior:
I have tested the connection to postgresql service and minio service in my k8s cluster. They all work. From the error msg it is clear that it is trying to connect to amaon-aws.
The text was updated successfully, but these errors were encountered: