Github user sujith71955 commented on the issue:

    https://github.com/apache/spark/pull/20611
  
    As above changes are applicable only for hdfs related paths, i did testing 
manually, please find the attached test report
    Usecase 1: Load data by specifying wild card character in the hdfs file path
    HDFS path details
    
![hdfs](https://user-images.githubusercontent.com/12999161/37136046-eac49bba-22c5-11e8-93ab-cd6ad485c387.PNG)
    load command output file level
    
![load_file](https://user-images.githubusercontent.com/12999161/37136153-661f53e0-22c6-11e8-9b8e-bd66841b2c42.PNG)
    
    Usecase 2: Load data by specifying wild card character in the hdfs folder 
path
    HDFS path details
    
![hdfs1](https://user-images.githubusercontent.com/12999161/37136233-b95be0f0-22c6-11e8-9ae0-82799d45639c.PNG)
    load command output folder level
    
![load_folderlevel](https://user-images.githubusercontent.com/12999161/37136284-f494bf70-22c6-11e8-91e3-b43c21d66ed4.PNG)
    
    Usecase 3: Negative case - Load data by specifying wild card character in 
the wrong hdfs file path
    
![spark-file_level](https://user-images.githubusercontent.com/12999161/37136344-2ee58f42-22c7-11e8-9d0b-1298d120538f.PNG)
    
    Usecase 4: Negative case - Load data by specifying wild card character in 
the wrong hdfs folder path
    
![spark-folder_level](https://user-images.githubusercontent.com/12999161/37136352-3fed88d0-22c7-11e8-9807-2b7fba2a5aec.PNG)
     



---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to