falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-102) Add integration tests for feed entity parser with table defined
Date Sat, 07 Sep 2013 09:55:51 GMT

    [ https://issues.apache.org/jira/browse/FALCON-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760977#comment-13760977

Srikanth Sundarrajan commented on FALCON-102:

Thats correct. I try to deduce this from the path containing the type.
Say: /data/foo is DATA, /stats/bar is STATS, etc. Defaults to DATA if path has no type information.
I think I can send the type information as well and let storage parse it out and give me a
list of locations instead of doing the current way. More refactoring.
If we pass the type & path, then the consumer can choose to do whatever they want with

Instead of custom parsing, I construct an URI and its not friendly with ${}. Hence the kludge.
Initially, I had it as an URI but was not sure of the pattern and now that we have fixed it,
may be it may make sense. Not sure how much it can buy us. In any case, this needs to be repeated
anyways to parse the various parts into database, table & partitions.
This is still a bit unclear to me. What is the significance of _Q__START or CLOSE in uri.
When do they show up and why do we need to replace them. Are these specific to the thrift
urls that catalog needs ?
> Add integration tests for feed entity parser with table defined
> ---------------------------------------------------------------
>                 Key: FALCON-102
>                 URL: https://issues.apache.org/jira/browse/FALCON-102
>             Project: Falcon
>          Issue Type: Sub-task
>    Affects Versions: 0.3
>            Reporter: Venkatesh Seetharam
>            Assignee: Venkatesh Seetharam
>         Attachments: FALCON-102.patch
> Having issues to get webhcat up and running. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message