hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Budianto Lie (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-894) DBInputformat not working with SQLServer
Date Mon, 21 Sep 2009 14:12:16 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757899#action_12757899

Budianto Lie commented on MAPREDUCE-894:

"SELECT ROW_NUMBER() OVER (ORDER BY .... ASC)" is a valid SQL statement.
ASC is just to make sure the order is ascending, and only need to put one after end of field

To test this new module, I populate some data in table and create a simple map-reduce application.
This application will read the data from table using DBInputFormat, do a simple process and
put the result in file. 
After that, checking the result file to see the result is correct.
In this case, I used SQL Server 2005 express edition.

> DBInputformat not working with SQLServer
> ----------------------------------------
>                 Key: MAPREDUCE-894
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-894
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>    Affects Versions: 0.21.0
>            Reporter: Budianto Lie
>            Assignee: Budianto Lie
>         Attachments: MAPREDUCE-894.2.patch, MAPREDUCE-894.patch
> org.apache.hadoop.mapreduce.lib.db.DBInputFormat
> Microsoft SQLServer doesn't support LIMIT and OFFSET.
> Fix:
> Based on MAPREDUCE-716, I already implemented it.
> By creating a new class org.apache.hadoop.mapreduce.lib.db.MsSqlDBRecordReader 
> and modifying class org.apache.hadoop.mapreduce.lib.db.DBInputFormat 
> Note: this fix is working only with SQLServer 2005 or higher.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message