BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
SangaviS
Obsidian | Level 7

We are getting the following error when trying to connect to hadoop adp

 

ERROR: Execute error: org.apache.hive.service.cli.HiveSQLException: Error while compiling statement: FAILED: SemanticException Line

       1:17 Invalid path ''/tmp/sasdata-2019-07-17-09-49-56-164-e-00001.dlv'': No files matching path

       hdfs://hcadps01hann/tmp/sasdata-2019-07-17-09-49-56-164-e-00001.dlv

 

Can someone help resolve this ?

1 ACCEPTED SOLUTION

Accepted Solutions
SangaviS
Obsidian | Level 7

The actual issue was that the jar files were not set up for this environment. The issue got resolved after setting them up. It was also missing a mapping folder on Hadoop end where the datasets would sit but that was not the actual root cause.

View solution in original post

4 REPLIES 4
AnandVyas
Ammonite | Level 13

Hi @SangaviS ,

 

Errors during SAS/Access Interface Hadoop connection can be very generic sometimes so it is best to work with hadoop admin team to resolve this kind of issues. In order to further troubleshoot I would suggest you to try below options.

 

1) Check if the connection is working out of SAS using beeline. If it's working then try to form libname statement using that.

2) Check if the user trying to connect hive has write access on /tmp HDFS file system.

3)  Add extra trace logging options to the code. ->  options sastrace=',,d,' sastraceloc=saslog nostsuffix;

sample can be found here: https://go.documentation.sas.com/?docsetId=engfedsrv&docsetTarget=n167fxh8cc9h2an198cln7b46vb9.htm&d...

 

-AV

SangaviS
Obsidian | Level 7
Thank you! Mapping folder was not set up properly on the Hadoop end. It got resolved after setting it up.


SimonDawson
SAS Employee

@SangaviS it would be awesome if you could document a little bit of what you did and tag your post as the answer to make it easier for others to find the solution in this thread if they have a similar error. Thanks.

SangaviS
Obsidian | Level 7

The actual issue was that the jar files were not set up for this environment. The issue got resolved after setting them up. It was also missing a mapping folder on Hadoop end where the datasets would sit but that was not the actual root cause.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 4 replies
  • 3310 views
  • 6 likes
  • 3 in conversation