Skip to content
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

TypeError: string indices must be integers (apache-airflow-providers-snowflake==4.0.2rc1) [BUG] #1351

Closed
mag3141592 opened this issue Dec 2, 2022 · 0 comments
Assignees
Labels
priority/high High priority
Milestone

Comments

@mag3141592
Copy link

Describe the bug
Similar to #1335 but with apache-airflow-providers-snowflake==4.0.2rc1

Screen Shot 2022-12-02 at 11 51 11 AM

Version

  • Astro-SDK: 1.3.0
  • Airflow version: 2.4.3+astro.1

To Reproduce
Steps to reproduce the behavior:

  1. Create connection "snowflake_default"
  2. Run DAG:
from datetime import datetime

from airflow import DAG

from astro import sql as aql
from astro.table import Table

SNOWFLAKE_CONN_ID = 'snowflake_default'

START_DATE = datetime(2000, 1, 1)

def query() -> Table:
    return "SELECT 'hi'"

with DAG(
    "example_transform",
    schedule_interval=None,
    start_date=START_DATE,
    catchup=False,
) as dag:

    get_data = aql.transform(
            conn_id=SNOWFLAKE_CONN_ID,
            task_id="query_data",
        )(query)() 
@mag3141592 mag3141592 changed the title TypeError: string indices must be integers (apache-airflow-providers-snowflake==4.0.2rc1) TypeError: string indices must be integers (apache-airflow-providers-snowflake==4.0.2rc1) [BUG] Dec 2, 2022
@phanikumv phanikumv added this to the 1.3.1 milestone Dec 8, 2022
@phanikumv phanikumv added the priority/high High priority label Dec 8, 2022
utkarsharma2 added a commit that referenced this issue Dec 15, 2022
# Description
## What is the current behavior?
Right now we don't have a check to make sure the rows returned by
handler

related: #1232
related: #1351

## What is the new behavior?
Added a check to make sure the object returned by the handler is not
None and is iterable.

## Does this introduce a breaking change?
Nope
utkarsharma2 added a commit that referenced this issue Dec 15, 2022
# Description
## What is the current behavior?
Right now we don't have a check to make sure the rows returned by
handler

related: #1232
related: #1351

## What is the new behavior?
Added a check to make sure the object returned by the handler is not
None and is iterable.

## Does this introduce a breaking change?
Nope
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/high High priority
Projects
None yet
Development

No branches or pull requests

4 participants