microsoft / microsoft/PowerPlatformConnectors
[BUG] Snowflake connector not partition aware
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 1.5k
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 11
Description
Type of Connector
Certified Connector
Name of Connector
Snowflake
Describe the bug
When retrieving more than 1k records of data the connector only returns the data contained within the first partition created by the Snowflake API. The rest of the records in subsequent partitions are not returned and ignored by the connector.
Is this a security bug?
No, this is not a security bug
What is the severity of this bug?
Severity 1 - Connector is broken or there's a very serious issue
To Reproduce
Create an instance of the connector in Power Automate
Query a Snowflake table with more than 1k records
Count records returned to Power Automate and Power Apps
Records will be less than total contained in Snowflake table
Expected behavior
the connector should traverse all partitions that are created by the Snowflake API so that the records returned match the number of records contained in the table.
Environment summary
Power Apps
Power Automate
Snowflake
Additional context
No additional context
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the Snowflake connector entry point and reproduce a query against a table with more than 1k records in Power Automate or Power Apps. Trace how the Snowflake API response is handled across partitions; done means records from every created partition are returned and the total matches the Snowflake table.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100