<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: no sas data written to Hadoop, only metadata BY USING IMPALA in New SAS User</title>
    <link>https://communities.sas.com/t5/New-SAS-User/no-sas-data-written-to-Hadoop-only-metadata-BY-USING-IMPALA/m-p/616110#M18846</link>
    <description>&lt;P&gt;Few things you can try to check the root cause:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. Execute INVALIDATE METADATA statement in your Impala SQL Clients or using Proc SQL Explicit passthrough, sometimes you've to perform this step to get a change reflected in your session, for more details you can reference:&lt;BR /&gt;&lt;A href="https://impala.apache.org/docs/build/html/topics/impala_invalidate_metadata.html" target="_blank"&gt;https://impala.apache.org/docs/build/html/topics/impala_invalidate_metadata.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. Check the table stats using Proc Contents&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;3. Last thing is enable the DBMS specific logging,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;for example you can run this statement to get a detailed log about database activity:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;options sastrace="d,d,d,d";&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 09 Jan 2020 05:55:15 GMT</pubDate>
    <dc:creator>Kalind_Patel</dc:creator>
    <dc:date>2020-01-09T05:55:15Z</dc:date>
    <item>
      <title>no sas data written to Hadoop, only metadata BY USING IMPALA</title>
      <link>https://communities.sas.com/t5/New-SAS-User/no-sas-data-written-to-Hadoop-only-metadata-BY-USING-IMPALA/m-p/616100#M18845</link>
      <description>&lt;P&gt;Here is my coding:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;libname IPCSIMPA impala dsn = "impala_hadoop_ipcs" schema="myipcs_cdm_raw";&lt;/P&gt;
&lt;P&gt;proc sql;&lt;BR /&gt;create table IPCSIMPA.E11&lt;BR /&gt;as select * from SASDATA.DATABASE_E1_RSTUDIO;&lt;BR /&gt;quit;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;here is sas log:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1 ;*';*";*/;quit;run;&lt;BR /&gt;2 OPTIONS LS=64 PS=15;&lt;BR /&gt;3 OPTIONS PAGENO=MIN;&lt;BR /&gt;4 %LET _CLIENTTASKLABEL='Program (5)';&lt;BR /&gt;5 %LET _CLIENTPROCESSFLOWNAME='Process Flow';&lt;BR /&gt;6 %LET&lt;BR /&gt;6 ! _CLIENTPROJECTPATH='C:\Users\ipcs_sasdemo\Documents\M&lt;BR /&gt;6 ! y SAS Files\Danial_MyIPCS\Hadoop_trial.egp';&lt;BR /&gt;7 %LET&lt;BR /&gt;7 ! _CLIENTPROJECTPATHHOST='SASMYIPCSOA01.stats.gov.my';&lt;BR /&gt;8 %LET _CLIENTPROJECTNAME='Hadoop_trial.egp';&lt;BR /&gt;2 The SAS System&lt;BR /&gt;10:00 Thursday, January 9, 2020&lt;/P&gt;
&lt;P&gt;9 %LET _SASPROGRAMFILE='';&lt;BR /&gt;10 %LET _SASPROGRAMFILEHOST='';&lt;BR /&gt;11 &lt;BR /&gt;12 ODS _ALL_ CLOSE;&lt;BR /&gt;13 OPTIONS DEV=PNG;&lt;BR /&gt;14 GOPTIONS XPIXELS=0 YPIXELS=0;&lt;BR /&gt;15 FILENAME EGRTF TEMP;&lt;BR /&gt;16 ODS RTF(ID=EGRTF) FILE=EGRTF&lt;BR /&gt;17 ENCODING='utf-8'&lt;BR /&gt;18 STYLE=Journal2&lt;BR /&gt;19 NOGTITLE&lt;BR /&gt;20 NOGFOOTNOTE&lt;BR /&gt;3 The SAS System&lt;BR /&gt;10:00 Thursday, January 9, 2020&lt;/P&gt;
&lt;P&gt;21 KEEPN&lt;BR /&gt;22 ;&lt;BR /&gt;NOTE: Writing RTF Body file: EGRTF&lt;BR /&gt;23 FILENAME EGSR TEMP;&lt;BR /&gt;24 ODS tagsets.sasreport13(ID=EGSR) FILE=EGSR&lt;BR /&gt;25 STYLE=Journal2&lt;BR /&gt;26 STYLESHEET=(URL="file:///C:/Program%20Files/SASHo&lt;BR /&gt;26 ! me/SASEnterpriseGuide/7.1/Styles/Journal2.css")&lt;BR /&gt;27 NOGTITLE&lt;BR /&gt;28 NOGFOOTNOTE&lt;BR /&gt;29 GPATH=&amp;amp;sasworklocation&lt;BR /&gt;30 ENCODING=UTF8&lt;BR /&gt;4 The SAS System&lt;BR /&gt;10:00 Thursday, January 9, 2020&lt;/P&gt;
&lt;P&gt;31 options(rolap="on")&lt;BR /&gt;32 ;&lt;BR /&gt;NOTE: Writing TAGSETS.SASREPORT13(EGSR) Body file: EGSR&lt;BR /&gt;33 FILENAME EGXLSSX TEMP;&lt;BR /&gt;34 ODS EXCEL(ID=EGXLSSX) FILE=EGXLSSX STYLE=Excel&lt;BR /&gt;35 OPTIONS (&lt;BR /&gt;36 EMBEDDED_TITLES="no" EMBEDDED_FOOTNOTES="no"&lt;BR /&gt;36 ! SHEET_INTERVAL="None"&lt;BR /&gt;37 );&lt;BR /&gt;38 &lt;BR /&gt;39 GOPTIONS ACCESSIBLE;&lt;BR /&gt;40 /* Insert custom code before submitted code here */&lt;BR /&gt;5 The SAS System&lt;BR /&gt;10:00 Thursday, January 9, 2020&lt;/P&gt;
&lt;P&gt;41 LIBNAME MYDATA 'C:\EG DATA';&lt;BR /&gt;NOTE: Library MYDATA does not exist.&lt;BR /&gt;42 &lt;BR /&gt;43 libname IPCSIMPA impala dsn = "impala_hadoop_ipcs"&lt;BR /&gt;43 ! schema="myipcs_cdm_raw";&lt;BR /&gt;NOTE: Libref IPCSIMPA was successfully assigned as follows: &lt;BR /&gt;Engine: IMPALA &lt;BR /&gt;Physical Name: impala_hadoop_ipcs&lt;BR /&gt;44 &lt;BR /&gt;45 proc sql;&lt;BR /&gt;46 create table IPCSIMPA.E15&lt;BR /&gt;47 as select * from SASDATA.DATABASE_E1_RSTUDIO;&lt;BR /&gt;6 The SAS System&lt;BR /&gt;10:00 Thursday, January 9, 2020&lt;/P&gt;
&lt;P&gt;NOTE: SAS variable labels, formats, and lengths are not written &lt;BR /&gt;to DBMS tables.&lt;BR /&gt;NOTE: Table IPCSIMPA.E15 created, with 512 rows and 9 columns.&lt;/P&gt;
&lt;P&gt;48 quit;&lt;BR /&gt;NOTE: PROCEDURE SQL used (Total process time):&lt;BR /&gt;real time 1.16 seconds&lt;BR /&gt;cpu time 0.03 seconds&lt;/P&gt;
&lt;P&gt;49 &lt;BR /&gt;50 GOPTIONS NOACCESSIBLE;&lt;BR /&gt;7 The SAS System&lt;BR /&gt;10:00 Thursday, January 9, 2020&lt;/P&gt;
&lt;P&gt;51 %LET _CLIENTTASKLABEL=;&lt;BR /&gt;52 %LET _CLIENTPROCESSFLOWNAME=;&lt;BR /&gt;53 %LET _CLIENTPROJECTPATH=;&lt;BR /&gt;54 %LET _CLIENTPROJECTPATHHOST=;&lt;BR /&gt;55 %LET _CLIENTPROJECTNAME=;&lt;BR /&gt;56 %LET _SASPROGRAMFILE=;&lt;BR /&gt;57 %LET _SASPROGRAMFILEHOST=;&lt;BR /&gt;58 &lt;BR /&gt;59 ;*';*";*/;quit;run;&lt;BR /&gt;60 ODS _ALL_ CLOSE;&lt;BR /&gt;NOTE: Writing EXCEL(EGXLSSX) file: &lt;BR /&gt;C:\Users\IPCS_S~1\AppData\Local\Temp\SAS Temporary &lt;BR /&gt;8 The SAS System&lt;BR /&gt;10:00 Thursday, January 9, 2020&lt;/P&gt;
&lt;P&gt;Files\_TD9736_SASMYIPCSOA01_\#LN01219&lt;BR /&gt;61 &lt;BR /&gt;62 &lt;BR /&gt;63 QUIT; RUN;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;the picture is output.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Capture.JPG" style="width: 600px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/35228iEA31E99344F2A158/image-size/large?v=v2&amp;amp;px=999" role="button" title="Capture.JPG" alt="Capture.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;what must i do??&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jan 2020 09:47:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/no-sas-data-written-to-Hadoop-only-metadata-BY-USING-IMPALA/m-p/616100#M18845</guid>
      <dc:creator>merahilyana</dc:creator>
      <dc:date>2020-01-09T09:47:30Z</dc:date>
    </item>
    <item>
      <title>Re: no sas data written to Hadoop, only metadata BY USING IMPALA</title>
      <link>https://communities.sas.com/t5/New-SAS-User/no-sas-data-written-to-Hadoop-only-metadata-BY-USING-IMPALA/m-p/616110#M18846</link>
      <description>&lt;P&gt;Few things you can try to check the root cause:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. Execute INVALIDATE METADATA statement in your Impala SQL Clients or using Proc SQL Explicit passthrough, sometimes you've to perform this step to get a change reflected in your session, for more details you can reference:&lt;BR /&gt;&lt;A href="https://impala.apache.org/docs/build/html/topics/impala_invalidate_metadata.html" target="_blank"&gt;https://impala.apache.org/docs/build/html/topics/impala_invalidate_metadata.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. Check the table stats using Proc Contents&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;3. Last thing is enable the DBMS specific logging,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;for example you can run this statement to get a detailed log about database activity:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;options sastrace="d,d,d,d";&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jan 2020 05:55:15 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/no-sas-data-written-to-Hadoop-only-metadata-BY-USING-IMPALA/m-p/616110#M18846</guid>
      <dc:creator>Kalind_Patel</dc:creator>
      <dc:date>2020-01-09T05:55:15Z</dc:date>
    </item>
    <item>
      <title>Re: no sas data written to Hadoop, only metadata BY USING IMPALA</title>
      <link>https://communities.sas.com/t5/New-SAS-User/no-sas-data-written-to-Hadoop-only-metadata-BY-USING-IMPALA/m-p/616154#M18855</link>
      <description>ALL LIST YOU GIVE IS NOT HAVE PROBLEM AND I GET SOLVE MY PROBLEM. I HAVE ONE PROBLEM DATA APPEAR BUT NOT FULL ROW OF DATA APPEAR..&lt;BR /&gt;&lt;BR /&gt;FOR EXAMPLE: &lt;BR /&gt;ORIGINAL ROW DATA HAVE 512&lt;BR /&gt;BUT OUTPUT IN IMPALA ROW DATA ONLY 176&lt;BR /&gt;&lt;BR /&gt;WHY??</description>
      <pubDate>Thu, 09 Jan 2020 09:50:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/no-sas-data-written-to-Hadoop-only-metadata-BY-USING-IMPALA/m-p/616154#M18855</guid>
      <dc:creator>merahilyana</dc:creator>
      <dc:date>2020-01-09T09:50:55Z</dc:date>
    </item>
  </channel>
</rss>

