{"push_id":1837409868,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"363bfe30ba44852a8fac946a37032f76480f6f1b","before":"a9339db99f0620d4828eb903523be55dfbf2fb64","commits":[{"sha":"eb7a5a66bbd5837c01f13c76b68de2a6034976f3","author":{"name":"Zhenhua Wang","email":"e1bb7e32d2908d1daa3f64ed12aed842612a516d@163.com"},"message":"[TEST] Load test table based on case sensitivity\n\n## What changes were proposed in this pull request?\n\nIt is strange that we will get \"table not found\" error if **the first sql** uses upper case table names, when developers write tests with `TestHiveSingleton`, **although case insensitivity**. This is because in `TestHiveQueryExecution`, test tables are loaded based on exact matching instead of case sensitivity.\n\n## How was this patch tested?\n\nAdded a new test case.\n\nAuthor: Zhenhua Wang <wzh_zju@163.com>\n\nCloses #18504 from wzhfy/testHive.","distinct":true,"url":"https://api.github.com/repos/wangyum/spark/commits/eb7a5a66bbd5837c01f13c76b68de2a6034976f3"},{"sha":"17bdc36ef16a544b693c628db276fe32db87fe7a","author":{"name":"aokolnychyi","email":"80b8bc2ab0f5688882726e0a9fa7473aab0f0bba@sap.com"},"message":"[SPARK-21102][SQL] Refresh command is too aggressive in parsing\n\n### Idea\n\nThis PR adds validation to REFRESH sql statements. Currently, users can specify whatever they want as resource path. For example, spark.sql(\"REFRESH ! $ !\") will be executed without any exceptions.\n\n### Implementation\n\nI am not sure that my current implementation is the most optimal, so any feedback is appreciated. My first idea was to make the grammar as strict as possible. Unfortunately, there were some problems. I tried the approach below:\n\nSqlBase.g4\n```\n...\n    | REFRESH TABLE tableIdentifier                                    #refreshTable\n    | REFRESH resourcePath                                             #refreshResource\n...\n\nresourcePath\n    : STRING\n    | (IDENTIFIER | number | nonReserved | '/' | '-')+ // other symbols can be added if needed\n    ;\n```\nIt is not flexible enough and requires to explicitly mention all possible symbols. Therefore, I came up with the current approach that is implemented in the code.\n\nLet me know your opinion on which one is better.\n\nAuthor: aokolnychyi <anton.okolnychyi@sap.com>\n\nCloses #18368 from aokolnychyi/spark-21102.","distinct":true,"url":"https://api.github.com/repos/wangyum/spark/commits/17bdc36ef16a544b693c628db276fe32db87fe7a"},{"sha":"363bfe30ba44852a8fac946a37032f76480f6f1b","author":{"name":"Takeshi Yamamuro","email":"739de1dd84c0b15373ba5c69d21b9bea89463bb3@apache.org"},"message":"[SPARK-20073][SQL] Prints an explicit warning message in case of NULL-safe equals\n\n## What changes were proposed in this pull request?\nThis pr added code to print the same warning messages with `===` cases when using NULL-safe equals (`<=>`).\n\n## How was this patch tested?\nExisting tests.\n\nAuthor: Takeshi Yamamuro <yamamuro@apache.org>\n\nCloses #18436 from maropu/SPARK-20073.","distinct":true,"url":"https://api.github.com/repos/wangyum/spark/commits/363bfe30ba44852a8fac946a37032f76480f6f1b"}]}
{"actor":{"display_login":"wangyum"}}