<?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>question Wy data is not being profiled using waterline? in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Wy-data-is-not-being-profiled-using-waterline/m-p/130412#M93098</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have download Sandbox machine for waterlinedata and I am getting waterline UI with per-loaded/per-profiled data everything is working fine(default).&lt;/P&gt;&lt;P&gt;Now I want to profile some files which are present under &lt;STRONG&gt;/user/waterlinedata/newStaggingData directory.&lt;/STRONG&gt;After copying from local to HDFS I am running command&lt;STRONG&gt; ./waterline profileOnly &lt;/STRONG&gt;&lt;STRONG&gt;/user/waterlinedata/newStaggingData and &lt;/STRONG&gt;now accoding to my knowledge profiling is nothing but identify file format,calculate data quality matrics and store all details in inventory etc. but am not able to see such details in front of my files within waterline UI.&lt;/P&gt;&lt;P&gt;Please attached images.&lt;A href="https://community.cloudera.com/legacyfs/online/attachments/4889-capture1.png" target="_blank"&gt;capture1.png&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I know that after executing above command waterline runs map-reduce job and I am sure that it's running perfectly but still not getting any fileformat/data quality metrics in UI.&lt;/P&gt;&lt;P&gt;otherwise send me the steps to for how to profile data which are present inside of  particular directory.&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
    <pubDate>Fri, 16 Sep 2022 10:24:21 GMT</pubDate>
    <dc:creator>Manus</dc:creator>
    <dc:date>2022-09-16T10:24:21Z</dc:date>
    <item>
      <title>Wy data is not being profiled using waterline?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Wy-data-is-not-being-profiled-using-waterline/m-p/130412#M93098</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have download Sandbox machine for waterlinedata and I am getting waterline UI with per-loaded/per-profiled data everything is working fine(default).&lt;/P&gt;&lt;P&gt;Now I want to profile some files which are present under &lt;STRONG&gt;/user/waterlinedata/newStaggingData directory.&lt;/STRONG&gt;After copying from local to HDFS I am running command&lt;STRONG&gt; ./waterline profileOnly &lt;/STRONG&gt;&lt;STRONG&gt;/user/waterlinedata/newStaggingData and &lt;/STRONG&gt;now accoding to my knowledge profiling is nothing but identify file format,calculate data quality matrics and store all details in inventory etc. but am not able to see such details in front of my files within waterline UI.&lt;/P&gt;&lt;P&gt;Please attached images.&lt;A href="https://community.cloudera.com/legacyfs/online/attachments/4889-capture1.png" target="_blank"&gt;capture1.png&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I know that after executing above command waterline runs map-reduce job and I am sure that it's running perfectly but still not getting any fileformat/data quality metrics in UI.&lt;/P&gt;&lt;P&gt;otherwise send me the steps to for how to profile data which are present inside of  particular directory.&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 10:24:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Wy-data-is-not-being-profiled-using-waterline/m-p/130412#M93098</guid>
      <dc:creator>Manus</dc:creator>
      <dc:date>2022-09-16T10:24:21Z</dc:date>
    </item>
    <item>
      <title>Re: Wy data is not being profiled using waterline?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Wy-data-is-not-being-profiled-using-waterline/m-p/130413#M93099</link>
      <description>&lt;P&gt;Hi @Manoj Dhake,&lt;/P&gt;&lt;P&gt;Glad to seeing you using the Waterline sandbox. You have the command right: waterline profileOnly &amp;lt;HDFS dir&amp;gt;.&lt;/P&gt;&lt;P&gt;To see what happened when you ran the command, you can get a very high-level look from the Dashboard page in the Waterline UI. If that shows that the job ran successfully, you might try refreshing the browser page (a hard refresh such as a command-r or control-r might be needed). If the job doesn't appear in the dashboard or it shows that it failed, you can look for more details in the jobs log: /var/log/waterline/wdi-inventory.log. &lt;/P&gt;&lt;P&gt;Because the sandboxes are pretty limited, it may be that the job is running out of resources. The wdi-inventory.log and corresponding MapReduce logs should make that clear if its the case.&lt;/P&gt;&lt;P&gt;Carol Drummond&lt;/P&gt;&lt;P&gt;Waterline Data Technical Support&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jun 2016 09:22:15 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Wy-data-is-not-being-profiled-using-waterline/m-p/130413#M93099</guid>
      <dc:creator>Carol at Waterline</dc:creator>
      <dc:date>2016-06-10T09:22:15Z</dc:date>
    </item>
    <item>
      <title>Re: Wy data is not being profiled using waterline?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Wy-data-is-not-being-profiled-using-waterline/m-p/130414#M93100</link>
      <description>&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;I was running waterline jobs such as(profile job,tag job,lineage job) but while running that map-reduce code I was getting exceptions "Permission Denied error" on some waterline data directory so I resolved them by using&lt;/P&gt;&lt;P&gt;sudo -u waterlinedata hadoop fs -chmod 777 &amp;lt;directory name&amp;gt;&lt;/P&gt;&lt;P&gt;and everything is worked fine.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jun 2016 13:47:06 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Wy-data-is-not-being-profiled-using-waterline/m-p/130414#M93100</guid>
      <dc:creator>Manus</dc:creator>
      <dc:date>2016-06-13T13:47:06Z</dc:date>
    </item>
  </channel>
</rss>

