You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Viji (JIRA)" <ji...@apache.org> on 2012/09/26 09:12:08 UTC

[jira] [Created] (MAPREDUCE-4685) DBCount should not use ACCESS

Viji created MAPREDUCE-4685:
-------------------------------

             Summary: DBCount should not use ACCESS 
                 Key: MAPREDUCE-4685
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4685
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: examples
    Affects Versions: 2.0.0-alpha
            Reporter: Viji


DBCount uses ACCESS as table name which is not supported for Oracle DBs since it is a keyword in Oracle as per http://docs.oracle.com/cd/B10501_01/appdev.920/a42525/apb.htm

I will shortly post a patch to address this.

--
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

[jira] [Updated] (MAPREDUCE-4685) DBCount should not use ACCESS

Posted by "Viji (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Viji updated MAPREDUCE-4685:
----------------------------

    Attachment: MAPREDUCE-4685.patch

- Changed table name Access to HAccess.
- Included an 'if' statement to the create statements to allow for proper datatype usage based on DB used.
                
> DBCount should not use ACCESS 
> ------------------------------
>
>                 Key: MAPREDUCE-4685
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4685
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: examples
>    Affects Versions: 2.0.0-alpha
>            Reporter: Viji
>         Attachments: MAPREDUCE-4685.patch
>
>
> DBCount uses ACCESS as table name which is not supported for Oracle DBs since it is a keyword in Oracle as per http://docs.oracle.com/cd/B10501_01/appdev.920/a42525/apb.htm
> Also, BIGINT isn't supported.
> I will shortly post a patch to address this.

--
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

[jira] [Commented] (MAPREDUCE-4685) DBCount should not use ACCESS

Posted by "Harsh J (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463682#comment-13463682 ] 

Harsh J commented on MAPREDUCE-4685:
------------------------------------

bq. -1 tests included.

Doesn't look like we can test this change specific to Oracle. The changes look good to me as they don't seem to be causing any problems to already working DBs (only an if-oracle case seems to exist as a change here, and a DB table name change).

+1, committing.
                
> DBCount should not use ACCESS 
> ------------------------------
>
>                 Key: MAPREDUCE-4685
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4685
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: examples
>    Affects Versions: 2.0.0-alpha
>            Reporter: Viji
>         Attachments: MAPREDUCE-4685.patch
>
>
> DBCount uses ACCESS as table name which is not supported for Oracle DBs since it is a keyword in Oracle as per http://docs.oracle.com/cd/B10501_01/appdev.920/a42525/apb.htm
> Also, BIGINT isn't supported.
> I will shortly post a patch to address this.

--
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

[jira] [Commented] (MAPREDUCE-4685) DBCount should not use ACCESS

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463680#comment-13463680 ] 

Hadoop QA commented on MAPREDUCE-4685:
--------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12546673/MAPREDUCE-4685.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-examples.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2884//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2884//console

This message is automatically generated.
                
> DBCount should not use ACCESS 
> ------------------------------
>
>                 Key: MAPREDUCE-4685
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4685
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: examples
>    Affects Versions: 2.0.0-alpha
>            Reporter: Viji
>         Attachments: MAPREDUCE-4685.patch
>
>
> DBCount uses ACCESS as table name which is not supported for Oracle DBs since it is a keyword in Oracle as per http://docs.oracle.com/cd/B10501_01/appdev.920/a42525/apb.htm
> Also, BIGINT isn't supported.
> I will shortly post a patch to address this.

--
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

[jira] [Updated] (MAPREDUCE-4685) DBCount should not use ACCESS

Posted by "Viji (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Viji updated MAPREDUCE-4685:
----------------------------

    Description: 
DBCount uses ACCESS as table name which is not supported for Oracle DBs since it is a keyword in Oracle as per http://docs.oracle.com/cd/B10501_01/appdev.920/a42525/apb.htm

Also, BIGINT isn't supported.

I will shortly post a patch to address this.

  was:
DBCount uses ACCESS as table name which is not supported for Oracle DBs since it is a keyword in Oracle as per http://docs.oracle.com/cd/B10501_01/appdev.920/a42525/apb.htm

I will shortly post a patch to address this.

    
> DBCount should not use ACCESS 
> ------------------------------
>
>                 Key: MAPREDUCE-4685
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4685
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: examples
>    Affects Versions: 2.0.0-alpha
>            Reporter: Viji
>
> DBCount uses ACCESS as table name which is not supported for Oracle DBs since it is a keyword in Oracle as per http://docs.oracle.com/cd/B10501_01/appdev.920/a42525/apb.htm
> Also, BIGINT isn't supported.
> I will shortly post a patch to address this.

--
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

[jira] [Commented] (MAPREDUCE-4685) DBCount should not use ACCESS

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463729#comment-13463729 ] 

Hudson commented on MAPREDUCE-4685:
-----------------------------------

Integrated in Hadoop-Hdfs-trunk-Commit #2837 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2837/])
    MAPREDUCE-4685. DBCount should not use ACCESS. Contributed by Viji. (harsh) (Revision 1390372)

     Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1390372
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/DBCountPageView.java

                
> DBCount should not use ACCESS 
> ------------------------------
>
>                 Key: MAPREDUCE-4685
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4685
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: examples
>    Affects Versions: 2.0.0-alpha
>            Reporter: Viji
>             Fix For: 3.0.0
>
>         Attachments: MAPREDUCE-4685.patch
>
>
> DBCount uses ACCESS as table name which is not supported for Oracle DBs since it is a keyword in Oracle as per http://docs.oracle.com/cd/B10501_01/appdev.920/a42525/apb.htm
> Also, BIGINT isn't supported.
> I will shortly post a patch to address this.

--
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

[jira] [Commented] (MAPREDUCE-4685) DBCount should not use ACCESS

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463775#comment-13463775 ] 

Hudson commented on MAPREDUCE-4685:
-----------------------------------

Integrated in Hadoop-Hdfs-trunk #1177 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1177/])
    MAPREDUCE-4685. DBCount should not use ACCESS. Contributed by Viji. (harsh) (Revision 1390372)

     Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1390372
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/DBCountPageView.java

                
> DBCount should not use ACCESS 
> ------------------------------
>
>                 Key: MAPREDUCE-4685
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4685
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: examples
>    Affects Versions: 2.0.0-alpha
>            Reporter: Viji
>             Fix For: 3.0.0
>
>         Attachments: MAPREDUCE-4685.patch
>
>
> DBCount uses ACCESS as table name which is not supported for Oracle DBs since it is a keyword in Oracle as per http://docs.oracle.com/cd/B10501_01/appdev.920/a42525/apb.htm
> Also, BIGINT isn't supported.
> I will shortly post a patch to address this.

--
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

[jira] [Commented] (MAPREDUCE-4685) DBCount should not use ACCESS

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463746#comment-13463746 ] 

Hudson commented on MAPREDUCE-4685:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #2796 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2796/])
    MAPREDUCE-4685. DBCount should not use ACCESS. Contributed by Viji. (harsh) (Revision 1390372)

     Result = FAILURE
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1390372
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/DBCountPageView.java

                
> DBCount should not use ACCESS 
> ------------------------------
>
>                 Key: MAPREDUCE-4685
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4685
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: examples
>    Affects Versions: 2.0.0-alpha
>            Reporter: Viji
>             Fix For: 3.0.0
>
>         Attachments: MAPREDUCE-4685.patch
>
>
> DBCount uses ACCESS as table name which is not supported for Oracle DBs since it is a keyword in Oracle as per http://docs.oracle.com/cd/B10501_01/appdev.920/a42525/apb.htm
> Also, BIGINT isn't supported.
> I will shortly post a patch to address this.

--
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

[jira] [Updated] (MAPREDUCE-4685) DBCount should not use ACCESS

Posted by "Viji (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Viji updated MAPREDUCE-4685:
----------------------------

    Status: Patch Available  (was: Open)
    
> DBCount should not use ACCESS 
> ------------------------------
>
>                 Key: MAPREDUCE-4685
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4685
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: examples
>    Affects Versions: 2.0.0-alpha
>            Reporter: Viji
>         Attachments: MAPREDUCE-4685.patch
>
>
> DBCount uses ACCESS as table name which is not supported for Oracle DBs since it is a keyword in Oracle as per http://docs.oracle.com/cd/B10501_01/appdev.920/a42525/apb.htm
> Also, BIGINT isn't supported.
> I will shortly post a patch to address this.

--
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

[jira] [Commented] (MAPREDUCE-4685) DBCount should not use ACCESS

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463724#comment-13463724 ] 

Hudson commented on MAPREDUCE-4685:
-----------------------------------

Integrated in Hadoop-Common-trunk-Commit #2774 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2774/])
    MAPREDUCE-4685. DBCount should not use ACCESS. Contributed by Viji. (harsh) (Revision 1390372)

     Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1390372
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/DBCountPageView.java

                
> DBCount should not use ACCESS 
> ------------------------------
>
>                 Key: MAPREDUCE-4685
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4685
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: examples
>    Affects Versions: 2.0.0-alpha
>            Reporter: Viji
>             Fix For: 3.0.0
>
>         Attachments: MAPREDUCE-4685.patch
>
>
> DBCount uses ACCESS as table name which is not supported for Oracle DBs since it is a keyword in Oracle as per http://docs.oracle.com/cd/B10501_01/appdev.920/a42525/apb.htm
> Also, BIGINT isn't supported.
> I will shortly post a patch to address this.

--
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

[jira] [Commented] (MAPREDUCE-4685) DBCount should not use ACCESS

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463823#comment-13463823 ] 

Hudson commented on MAPREDUCE-4685:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #1208 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1208/])
    MAPREDUCE-4685. DBCount should not use ACCESS. Contributed by Viji. (harsh) (Revision 1390372)

     Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1390372
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/DBCountPageView.java

                
> DBCount should not use ACCESS 
> ------------------------------
>
>                 Key: MAPREDUCE-4685
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4685
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: examples
>    Affects Versions: 2.0.0-alpha
>            Reporter: Viji
>             Fix For: 3.0.0
>
>         Attachments: MAPREDUCE-4685.patch
>
>
> DBCount uses ACCESS as table name which is not supported for Oracle DBs since it is a keyword in Oracle as per http://docs.oracle.com/cd/B10501_01/appdev.920/a42525/apb.htm
> Also, BIGINT isn't supported.
> I will shortly post a patch to address this.

--
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

[jira] [Updated] (MAPREDUCE-4685) DBCount should not use ACCESS

Posted by "Harsh J (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harsh J updated MAPREDUCE-4685:
-------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.0
           Status: Resolved  (was: Patch Available)

Committed to trunk, thanks for the report and the patch Viji! Hope to see more contributions from you :)
                
> DBCount should not use ACCESS 
> ------------------------------
>
>                 Key: MAPREDUCE-4685
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4685
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: examples
>    Affects Versions: 2.0.0-alpha
>            Reporter: Viji
>             Fix For: 3.0.0
>
>         Attachments: MAPREDUCE-4685.patch
>
>
> DBCount uses ACCESS as table name which is not supported for Oracle DBs since it is a keyword in Oracle as per http://docs.oracle.com/cd/B10501_01/appdev.920/a42525/apb.htm
> Also, BIGINT isn't supported.
> I will shortly post a patch to address this.

--
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