Add support for Query Hints for MS Fabric in TSql170Parser

Open

#180 opened on Nov 3, 2025 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 48/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: csharp, sql
Domain: compilers

Research direction

Start with the TSql170Parser entry point and the C# reproduction in the issue, using the Microsoft Fabric Query Hints examples as inputs. Trace the parser errors for FOR TIMESTAMP AS OF, FORCE SINGLE NODE PLAN, and FORCE DISTRIBUTED PLAN; done means all three examples parse without errors.

Written by the indexing model from the issue text.

Description

sqldw

We have encountered a parsing issue in Microsoft Documentation for MS Fabric Query Hints using TSql170Parser 170.128.0.

Examples
FOR TIMESTAMP AS OF

SELECT OrderDateKey, SUM(SalesAmount) AS TotalSales
FROM FactInternetSales
GROUP BY OrderDateKey
ORDER BY OrderDateKey
OPTION (FOR TIMESTAMP AS OF '2024-03-13T19:39:35.28');--March 13, 2024 at 7:39:35.28 PM UTC

Error Message : Incorrect syntax near 'FOR'.

Query force a single node or distributed query

SELECT OrderDateKey, SalesAmount
FROM FactInternetSales
OPTION (FORCE SINGLE NODE PLAN);

Error Message : Incorrect syntax near 'NODE'.

SELECT OrderDateKey, SalesAmount
FROM FactInternetSales
OPTION (FORCE DISTRIBUTED PLAN);

Error Message : Incorrect syntax near 'FORCE'.

Steps to reproduce

        static void Main(string[] args)
        {
            var script = @"<EXAMPLE_SCRIPT>";

            var parser = new TSql170Parser(true, 0);
            var fragment = parser.Parse(new StringReader(script), out var parseErrors);

            if (parseErrors.Count > 0)
            {
                Console.WriteLine(parseErrors[0].Message);
            }
        }

Dominant language: GAP
Stars: 277
Forks: 43
Avg merge: 6d 17h
Merged PRs (30d): 3

Contributor guide

Open the contributing guide

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.

Similar issues

perf: a definite-value return type (`--> Nil`, `--> True`) sends every call down the full path (~12 µs vs ~1 µs) Open

todo:perf

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

tokuhirom/mutsu#9074 · Opened Sep 22, 2026
StUnhex.number() misformats Long.MIN_VALUE as scientific notation instead of a plain integer Open

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

objectionary/eo#8894 · Opened Sep 22, 2026
PHIE parser rejects the empty object representation Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

objectionary/phie#154 · Opened Sep 22, 2026
`EoCodec` stores a `float` as a `double`, so a signaling-NaN float constant comes back with different bits Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

objectionary/jeo-maven-plugin#1774 · Opened Sep 21, 2026
Minor breakage w/ LLVM 7: `test_llvm.cpp: error: cannot convert 'llvm::Module' to 'llvm::Module*'` Open

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

lfortran/lfortran#13384 · Opened Sep 21, 2026

More Compilers issues