Scalar function for url encoding and decoding#8378
Scalar function for url encoding and decoding#8378Jackie-Jiang merged 4 commits intoapache:masterfrom
Conversation
9d12d16 to
71d2e7b
Compare
Codecov Report
@@ Coverage Diff @@
## master #8378 +/- ##
============================================
- Coverage 70.79% 61.07% -9.73%
+ Complexity 4264 4192 -72
============================================
Files 1640 1640
Lines 85931 86228 +297
Branches 12922 13035 +113
============================================
- Hits 60837 52664 -8173
- Misses 20899 29679 +8780
+ Partials 4195 3885 -310
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
| .compileToPinotQuery("SELECT ago('PT1H'), fromDateTime('2020-01-01 UTC', 'yyyy-MM-dd z') FROM myTable"))); | ||
| Assert.assertFalse(BaseBrokerRequestHandler | ||
| .isLiteralOnlyQuery(CalciteSqlParser.compileToPinotQuery("SELECT count(*) from foo where bar > ago('PT1H')"))); | ||
| Assert.assertTrue(BaseBrokerRequestHandler.isLiteralOnlyQuery(CalciteSqlParser |
There was a problem hiding this comment.
Should we not use full URLs as inputs to encodeUrl / decodeUrl functions in tests ? From user perspective, they will use the full URL right ?
SELECT encodeUrl(<myURL>) FROM FOO .....
There was a problem hiding this comment.
@jasperjiaguo - please add test cases with real URLs as well
There was a problem hiding this comment.
Sorry, I merged the PR too soon. @jasperjiaguo Can you please address Sidd's comments in a separate PR?
Description
Add scalar functions to perform url encoding and decoding in queries.
Upgrade Notes
Does this PR prevent a zero down-time upgrade? (Assume upgrade order: Controller, Broker, Server, Minion)
No