Count query fails if a large query ends in a comment

[oglehb]

Describe the bug
When the final line of a Kusto query ends with a comment, the count query fails if the tabular expression result contains more than truncationmaxrecords rows (500000 by default).

To Reproduce

conn = {
    "kustoCluster": xxx,
    "kustoDatabase": xxx,
    "kustoAadAppId": xxx,
    "kustoAadAppSecret": xxx,
    "kustoAadAuthorityID": xxx,
}
crp = '{"Options": {"truncationmaxrecords": 500000}, "Parameters": {}}'
kql = 'range _ from 1 to 500001 step 1 // this comment causes issue'

df = (spark.read
        .format("com.microsoft.kusto.spark.synapse.datasource")
        .options(**conn)
        .option("kustoQuery", kql)
        .option("clientRequestPropertiesJson", crp)
        .load())

df.limit(0)

Expected behavior
All else the same, I expected the query range _ from 1 to 500001 step 1 // this comment causes issue to behave identically to the query range _ from 1 to 500001 step 1 (when truncationmaxrecords is 500000 or below in this case).

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• Spark v3.2 on Synapse

Additional context
Maybe it has something to do with this code:

azure-kusto-spark/connector/src/main/scala/com/microsoft/kusto/spark/utils/KustoQueryUtils.scala

Lines 11 to 13 in 83cf263

	def limitQuery(query: String, limit: Int): String = {
	query + s"| take $limit"
	}

Perhaps changing would solve the issue:

def limitQuery(query: String, limit: Int): String = {
    val trimmedQuery = query.trim
    trimmedQuery + s"\n| take $limit"
}

(I do not know Scala)

[ag-ramachandran]

Hello @oglehb , Will have a look at this right away and potentially fixing this issue