microsoft / microsoft/go-sqlcmd

Add ability to import/export data to/from Parquet files with SQLCMD

Open
#486 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
595
Forks
91
Avg merge
9h 35m
Merged PRs (30d)
1

Description

Creating this placeholder for the investigation of adding import/export functionality to go-sqlcmd.

Main use cases would include:

  1. Output SQL Server query results to parquet files
  2. Read data from parquet files for display of some or all rows on screen to check contents of file
  3. Read data from parquet files and insert into table in SQL Server database
  4. Be able to read both standalone parquet files as well as delta
  5. Perform basic filtering via SQL-like where clause or regex by column

Additional possibilities include:

  1. Output SQL Server query results to json, csv, xls files
  2. Convert json, csv, xls to parquet
  3. Convert parquet, including delta, to json, csv, xls
  4. Convert subset of rows between formats - ex: "Take customer data from delta store and export all customers in Chicago to xls"

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by narrowing the requested Parquet and Delta import/export scope for go-sqlcmd, then define supported commands, filtering behavior, and verification cases as the completion criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, sql
Domain
cli, data, database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.