You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@lens.apache.org by "Deepak Kumar Barr (Tech_BLR)" <de...@flipkart.com> on 2015/07/07 14:02:13 UTC

File size in the /resultset api response

Hey All,

   In case of persistent resultset,
*/queryapi/queries/{queryHandle}/resultset* response contains the resultset
HDFS path and the number of rows in the resultset.

      I was wondering if we could also include the size of hdfs resultset
file in the response. The information on the size of the file can be
obtained using WebHDFS APIs. I think this information could be useful for
the user. What do you guys think ?

Regards,
Deepak Kumar Barr

-- 


------------------------------------------------------------------------------------------------------------------------------------------

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If you have received this email in error please notify the system manager. 
This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system. If you are not the intended recipient 
you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly 
prohibited. Although Flipkart has taken reasonable precautions to ensure no 
viruses are present in this email, the company cannot accept responsibility 
for any loss or damage arising from the use of this email or attachments

Re: File size in the /resultset api response

Posted by "Deepak Kumar Barr (Tech_BLR)" <de...@flipkart.com>.
Jaideep,

   I just looked at FileSystem APIs and I found that
FileSystem.getFileStatus().getLen() will give us the file size. This is
definitely a better option than webHDFS APIs. I will go ahead and create a
JIRA for this.

Regards,
Deepak Kumar Barr

On Wed, Jul 8, 2015 at 10:13 AM, Jaideep Dhok <ja...@inmobi.com>
wrote:

> Hi Deepak,
> File size is certainly useful for persistent result sets, but do we need
> WebHdfs for it? Its an extra server to run, can we get it from the
> FileSystem API itself?
>
> Thanks,
> Jaideep
>
> On Wed, Jul 8, 2015 at 10:05 AM, Sharad Agarwal <sh...@apache.org> wrote:
>
>> This should be useful. However file size will be available only for
>> persistent resultset.
>>
>> On Tue, Jul 7, 2015 at 5:32 PM, Deepak Kumar Barr (Tech_BLR) <
>> deepak.barr@flipkart.com> wrote:
>>
>> > Hey All,
>> >
>> >    In case of persistent resultset,
>> > */queryapi/queries/{queryHandle}/resultset* response contains the
>> > resultset HDFS path and the number of rows in the resultset.
>> >
>> >       I was wondering if we could also include the size of hdfs
>> resultset
>> > file in the response. The information on the size of the file can be
>> > obtained using WebHDFS APIs. I think this information could be useful
>> for
>> > the user. What do you guys think ?
>> >
>> > Regards,
>> > Deepak Kumar Barr
>> >
>> >
>> >
>> ------------------------------------------------------------------------------------------------------------------------------------------
>> >
>> > This email and any files transmitted with it are confidential and
>> intended
>> > solely for the use of the individual or entity to whom they are
>> addressed.
>> > If you have received this email in error please notify the system
>> manager.
>> > This message contains confidential information and is intended only for
>> the
>> > individual named. If you are not the named addressee you should not
>> > disseminate, distribute or copy this e-mail. Please notify the sender
>> > immediately by e-mail if you have received this e-mail by mistake and
>> > delete this e-mail from your system. If you are not the intended
>> recipient
>> > you are notified that disclosing, copying, distributing or taking any
>> > action in reliance on the contents of this information is strictly
>> > prohibited. Although Flipkart has taken reasonable precautions to
>> ensure no
>> > viruses are present in this email, the company cannot accept
>> responsibility
>> > for any loss or damage arising from the use of this email or attachments
>> >
>>
>
>
>
> --
> -
> Jaideep Dhok
>
> _____________________________________________________________
> The information contained in this communication is intended solely for the
> use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally privileged
> information. If you are not the intended recipient you are hereby notified
> that any disclosure, copying, distribution or taking any action in reliance
> on the contents of this information is strictly prohibited and may be
> unlawful. If you have received this communication in error, please notify
> us immediately by responding to this email and then delete it from your
> system. The firm is neither liable for the proper and complete transmission
> of the information contained in this communication nor for any delay in its
> receipt.

-- 


------------------------------------------------------------------------------------------------------------------------------------------

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If you have received this email in error please notify the system manager. 
This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system. If you are not the intended recipient 
you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly 
prohibited. Although Flipkart has taken reasonable precautions to ensure no 
viruses are present in this email, the company cannot accept responsibility 
for any loss or damage arising from the use of this email or attachments

Re: File size in the /resultset api response

Posted by "Deepak Kumar Barr (Tech_BLR)" <de...@flipkart.com>.
Jaideep,

   I just looked at FileSystem APIs and I found that
FileSystem.getFileStatus().getLen() will give us the file size. This is
definitely a better option than webHDFS APIs. I will go ahead and create a
JIRA for this.

Regards,
Deepak Kumar Barr

On Wed, Jul 8, 2015 at 10:13 AM, Jaideep Dhok <ja...@inmobi.com>
wrote:

> Hi Deepak,
> File size is certainly useful for persistent result sets, but do we need
> WebHdfs for it? Its an extra server to run, can we get it from the
> FileSystem API itself?
>
> Thanks,
> Jaideep
>
> On Wed, Jul 8, 2015 at 10:05 AM, Sharad Agarwal <sh...@apache.org> wrote:
>
>> This should be useful. However file size will be available only for
>> persistent resultset.
>>
>> On Tue, Jul 7, 2015 at 5:32 PM, Deepak Kumar Barr (Tech_BLR) <
>> deepak.barr@flipkart.com> wrote:
>>
>> > Hey All,
>> >
>> >    In case of persistent resultset,
>> > */queryapi/queries/{queryHandle}/resultset* response contains the
>> > resultset HDFS path and the number of rows in the resultset.
>> >
>> >       I was wondering if we could also include the size of hdfs
>> resultset
>> > file in the response. The information on the size of the file can be
>> > obtained using WebHDFS APIs. I think this information could be useful
>> for
>> > the user. What do you guys think ?
>> >
>> > Regards,
>> > Deepak Kumar Barr
>> >
>> >
>> >
>> ------------------------------------------------------------------------------------------------------------------------------------------
>> >
>> > This email and any files transmitted with it are confidential and
>> intended
>> > solely for the use of the individual or entity to whom they are
>> addressed.
>> > If you have received this email in error please notify the system
>> manager.
>> > This message contains confidential information and is intended only for
>> the
>> > individual named. If you are not the named addressee you should not
>> > disseminate, distribute or copy this e-mail. Please notify the sender
>> > immediately by e-mail if you have received this e-mail by mistake and
>> > delete this e-mail from your system. If you are not the intended
>> recipient
>> > you are notified that disclosing, copying, distributing or taking any
>> > action in reliance on the contents of this information is strictly
>> > prohibited. Although Flipkart has taken reasonable precautions to
>> ensure no
>> > viruses are present in this email, the company cannot accept
>> responsibility
>> > for any loss or damage arising from the use of this email or attachments
>> >
>>
>
>
>
> --
> -
> Jaideep Dhok
>
> _____________________________________________________________
> The information contained in this communication is intended solely for the
> use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally privileged
> information. If you are not the intended recipient you are hereby notified
> that any disclosure, copying, distribution or taking any action in reliance
> on the contents of this information is strictly prohibited and may be
> unlawful. If you have received this communication in error, please notify
> us immediately by responding to this email and then delete it from your
> system. The firm is neither liable for the proper and complete transmission
> of the information contained in this communication nor for any delay in its
> receipt.

-- 


------------------------------------------------------------------------------------------------------------------------------------------

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If you have received this email in error please notify the system manager. 
This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system. If you are not the intended recipient 
you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly 
prohibited. Although Flipkart has taken reasonable precautions to ensure no 
viruses are present in this email, the company cannot accept responsibility 
for any loss or damage arising from the use of this email or attachments

Re: File size in the /resultset api response

Posted by Jaideep Dhok <ja...@inmobi.com>.
Hi Deepak,
File size is certainly useful for persistent result sets, but do we need
WebHdfs for it? Its an extra server to run, can we get it from the
FileSystem API itself?

Thanks,
Jaideep

On Wed, Jul 8, 2015 at 10:05 AM, Sharad Agarwal <sh...@apache.org> wrote:

> This should be useful. However file size will be available only for
> persistent resultset.
>
> On Tue, Jul 7, 2015 at 5:32 PM, Deepak Kumar Barr (Tech_BLR) <
> deepak.barr@flipkart.com> wrote:
>
> > Hey All,
> >
> >    In case of persistent resultset,
> > */queryapi/queries/{queryHandle}/resultset* response contains the
> > resultset HDFS path and the number of rows in the resultset.
> >
> >       I was wondering if we could also include the size of hdfs resultset
> > file in the response. The information on the size of the file can be
> > obtained using WebHDFS APIs. I think this information could be useful for
> > the user. What do you guys think ?
> >
> > Regards,
> > Deepak Kumar Barr
> >
> >
> >
> ------------------------------------------------------------------------------------------------------------------------------------------
> >
> > This email and any files transmitted with it are confidential and
> intended
> > solely for the use of the individual or entity to whom they are
> addressed.
> > If you have received this email in error please notify the system
> manager.
> > This message contains confidential information and is intended only for
> the
> > individual named. If you are not the named addressee you should not
> > disseminate, distribute or copy this e-mail. Please notify the sender
> > immediately by e-mail if you have received this e-mail by mistake and
> > delete this e-mail from your system. If you are not the intended
> recipient
> > you are notified that disclosing, copying, distributing or taking any
> > action in reliance on the contents of this information is strictly
> > prohibited. Although Flipkart has taken reasonable precautions to ensure
> no
> > viruses are present in this email, the company cannot accept
> responsibility
> > for any loss or damage arising from the use of this email or attachments
> >
>



-- 
-
Jaideep Dhok

-- 
_____________________________________________________________
The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
on the contents of this information is strictly prohibited and may be 
unlawful. If you have received this communication in error, please notify 
us immediately by responding to this email and then delete it from your 
system. The firm is neither liable for the proper and complete transmission 
of the information contained in this communication nor for any delay in its 
receipt.

Re: File size in the /resultset api response

Posted by Jaideep Dhok <ja...@inmobi.com>.
Hi Deepak,
File size is certainly useful for persistent result sets, but do we need
WebHdfs for it? Its an extra server to run, can we get it from the
FileSystem API itself?

Thanks,
Jaideep

On Wed, Jul 8, 2015 at 10:05 AM, Sharad Agarwal <sh...@apache.org> wrote:

> This should be useful. However file size will be available only for
> persistent resultset.
>
> On Tue, Jul 7, 2015 at 5:32 PM, Deepak Kumar Barr (Tech_BLR) <
> deepak.barr@flipkart.com> wrote:
>
> > Hey All,
> >
> >    In case of persistent resultset,
> > */queryapi/queries/{queryHandle}/resultset* response contains the
> > resultset HDFS path and the number of rows in the resultset.
> >
> >       I was wondering if we could also include the size of hdfs resultset
> > file in the response. The information on the size of the file can be
> > obtained using WebHDFS APIs. I think this information could be useful for
> > the user. What do you guys think ?
> >
> > Regards,
> > Deepak Kumar Barr
> >
> >
> >
> ------------------------------------------------------------------------------------------------------------------------------------------
> >
> > This email and any files transmitted with it are confidential and
> intended
> > solely for the use of the individual or entity to whom they are
> addressed.
> > If you have received this email in error please notify the system
> manager.
> > This message contains confidential information and is intended only for
> the
> > individual named. If you are not the named addressee you should not
> > disseminate, distribute or copy this e-mail. Please notify the sender
> > immediately by e-mail if you have received this e-mail by mistake and
> > delete this e-mail from your system. If you are not the intended
> recipient
> > you are notified that disclosing, copying, distributing or taking any
> > action in reliance on the contents of this information is strictly
> > prohibited. Although Flipkart has taken reasonable precautions to ensure
> no
> > viruses are present in this email, the company cannot accept
> responsibility
> > for any loss or damage arising from the use of this email or attachments
> >
>



-- 
-
Jaideep Dhok

-- 
_____________________________________________________________
The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
on the contents of this information is strictly prohibited and may be 
unlawful. If you have received this communication in error, please notify 
us immediately by responding to this email and then delete it from your 
system. The firm is neither liable for the proper and complete transmission 
of the information contained in this communication nor for any delay in its 
receipt.

Re: File size in the /resultset api response

Posted by Sharad Agarwal <sh...@apache.org>.
This should be useful. However file size will be available only for
persistent resultset.

On Tue, Jul 7, 2015 at 5:32 PM, Deepak Kumar Barr (Tech_BLR) <
deepak.barr@flipkart.com> wrote:

> Hey All,
>
>    In case of persistent resultset,
> */queryapi/queries/{queryHandle}/resultset* response contains the
> resultset HDFS path and the number of rows in the resultset.
>
>       I was wondering if we could also include the size of hdfs resultset
> file in the response. The information on the size of the file can be
> obtained using WebHDFS APIs. I think this information could be useful for
> the user. What do you guys think ?
>
> Regards,
> Deepak Kumar Barr
>
>
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. If you are not the intended recipient
> you are notified that disclosing, copying, distributing or taking any
> action in reliance on the contents of this information is strictly
> prohibited. Although Flipkart has taken reasonable precautions to ensure no
> viruses are present in this email, the company cannot accept responsibility
> for any loss or damage arising from the use of this email or attachments
>

Re: File size in the /resultset api response

Posted by Sharad Agarwal <sh...@apache.org>.
This should be useful. However file size will be available only for
persistent resultset.

On Tue, Jul 7, 2015 at 5:32 PM, Deepak Kumar Barr (Tech_BLR) <
deepak.barr@flipkart.com> wrote:

> Hey All,
>
>    In case of persistent resultset,
> */queryapi/queries/{queryHandle}/resultset* response contains the
> resultset HDFS path and the number of rows in the resultset.
>
>       I was wondering if we could also include the size of hdfs resultset
> file in the response. The information on the size of the file can be
> obtained using WebHDFS APIs. I think this information could be useful for
> the user. What do you guys think ?
>
> Regards,
> Deepak Kumar Barr
>
>
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. If you are not the intended recipient
> you are notified that disclosing, copying, distributing or taking any
> action in reliance on the contents of this information is strictly
> prohibited. Although Flipkart has taken reasonable precautions to ensure no
> viruses are present in this email, the company cannot accept responsibility
> for any loss or damage arising from the use of this email or attachments
>