[jira] [Created] (HDFS-2075) Add Number of Reporting Nodes to namenode web UI
Add Number of Reporting Nodes to namenode web UI -- Key: HDFS-2075 URL: https://issues.apache.org/jira/browse/HDFS-2075 Project: Hadoop HDFS Issue Type: Improvement Components: name-node, tools Affects Versions: 0.20.2, 0.20.1 Reporter: Xing Jin Priority: Minor Fix For: 0.20.3 The namenode web UI misses some information when safemode is on (e.g., the number of reporting nodes). These information will help us understand the system status. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-2075) Add Number of Reporting Nodes to namenode web UI
[ https://issues.apache.org/jira/browse/HDFS-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xing Jin updated HDFS-2075: --- Attachment: HDFS-2075.patch.txt patch for the issue Add Number of Reporting Nodes to namenode web UI -- Key: HDFS-2075 URL: https://issues.apache.org/jira/browse/HDFS-2075 Project: Hadoop HDFS Issue Type: Improvement Components: name-node, tools Affects Versions: 0.20.1, 0.20.2 Reporter: Xing Jin Priority: Minor Fix For: 0.20.3 Attachments: HDFS-2075.patch.txt Original Estimate: 1h Remaining Estimate: 1h The namenode web UI misses some information when safemode is on (e.g., the number of reporting nodes). These information will help us understand the system status. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVE-1659) parse_url_tuple: a UDTF version of parse_url
[ https://issues.apache.org/jira/browse/HIVE-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xing Jin updated HIVE-1659: --- Attachment: HIVE-1659.patch This patch contains implementation of parse_url_tuple function, as well as a test file and a test output. parse_url_tuple: a UDTF version of parse_url - Key: HIVE-1659 URL: https://issues.apache.org/jira/browse/HIVE-1659 Project: Hadoop Hive Issue Type: New Feature Affects Versions: 0.5.0 Reporter: Ning Zhang Attachments: HIVE-1659.patch The UDF parse_url take s a URL, parse it and extract QUERY/PATH etc from it. However it can only extract an atomic value from the URL. If we want to extract multiple piece of information, we need to call the function many times. It is desirable to parse the URL once and extract all needed information and return a tuple in a UDTF. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1659) parse_url_tuple: a UDTF version of parse_url
[ https://issues.apache.org/jira/browse/HIVE-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xing Jin updated HIVE-1659: --- Attachment: HIVE-1659.patch2 generate patch after 'svn up' and in root directory parse_url_tuple: a UDTF version of parse_url - Key: HIVE-1659 URL: https://issues.apache.org/jira/browse/HIVE-1659 Project: Hadoop Hive Issue Type: New Feature Affects Versions: 0.5.0 Reporter: Ning Zhang Attachments: HIVE-1659.patch, HIVE-1659.patch2 The UDF parse_url take s a URL, parse it and extract QUERY/PATH etc from it. However it can only extract an atomic value from the URL. If we want to extract multiple piece of information, we need to call the function many times. It is desirable to parse the URL once and extract all needed information and return a tuple in a UDTF. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1659) parse_url_tuple: a UDTF version of parse_url
[ https://issues.apache.org/jira/browse/HIVE-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xing Jin updated HIVE-1659: --- Attachment: HIVE-1659.patch3 update show_functions.q and 'svn up' again. Thanks. Do I need to run all unitests on my machine? parse_url_tuple: a UDTF version of parse_url - Key: HIVE-1659 URL: https://issues.apache.org/jira/browse/HIVE-1659 Project: Hadoop Hive Issue Type: New Feature Affects Versions: 0.5.0 Reporter: Ning Zhang Attachments: HIVE-1659.patch, HIVE-1659.patch2, HIVE-1659.patch3 The UDF parse_url take s a URL, parse it and extract QUERY/PATH etc from it. However it can only extract an atomic value from the URL. If we want to extract multiple piece of information, we need to call the function many times. It is desirable to parse the URL once and extract all needed information and return a tuple in a UDTF. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1659) parse_url_tuple: a UDTF version of parse_url
[ https://issues.apache.org/jira/browse/HIVE-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xing Jin updated HIVE-1659: --- Status: Patch Available (was: Open) Affects Version/s: 0.5.0 Add new function parse_url_tuple for HIVE. parse_url_tuple: a UDTF version of parse_url - Key: HIVE-1659 URL: https://issues.apache.org/jira/browse/HIVE-1659 Project: Hadoop Hive Issue Type: New Feature Affects Versions: 0.5.0 Reporter: Ning Zhang The UDF parse_url take s a URL, parse it and extract QUERY/PATH etc from it. However it can only extract an atomic value from the URL. If we want to extract multiple piece of information, we need to call the function many times. It is desirable to parse the URL once and extract all needed information and return a tuple in a UDTF. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (AVRO-484) avro C++ HTTP rpc support
avro C++ HTTP rpc support - Key: AVRO-484 URL: https://issues.apache.org/jira/browse/AVRO-484 Project: Avro Issue Type: Improvement Components: c++ Reporter: Xing Jin Upon Scott Banachowski's request, this is to add HTTP transport support for the rpc usage of avro C++ version. The current implementation uses HTTP POST to send over a request body (of any content) and the server side responds with a standard HTTP response body (of any content). Current status: it only requires a user to provide a streambuf input and define a function that contains the business logic to generate the serialized content into a response streambuf. testhttpserver would be a good example there. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
