# ARP is so restrictive, I don't even want to use it anymore

**URL:** https://community.dremio.com/t/arp-is-so-restrictive-i-dont-even-want-to-use-it-anymore/5070
**Category:** Uncategorized
**Created:** [February 17, 2020, 3:33pm UTC](https://community.dremio.com/t/arp-is-so-restrictive-i-dont-even-want-to-use-it-anymore/5070 "2020-02-17T15:33:06Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![patricker](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/patricker/32/1823_2.png) [@patricker](https://community.dremio.com/u/patricker)
#### Post date: [February 19, 2020, 3:09am UTC](https://community.dremio.com/t/arp-is-so-restrictive-i-dont-even-want-to-use-it-anymore/5070/3 "2020-02-19T03:09:43Z")

</div>

Thanks for the guidance @Kyle_Porter, I agree it’s far from ideal, but matching the package name does indeed let me extend the class as you suggested. I don’t suppose you have a fix for JDBC drivers that don’t support `getTimestamp` with a Calendar object 🙂. I opened a question about that as well (I found it easier to modify the JDBC library than ARP…):

> [@Enhancement Request - ARP JDBC Data Type Mapping](https://community.dremio.com/t/enhancement-request-arp-jdbc-data-type-mapping/5032):
>
> When mapping data types, date and timestamp objects need to support NOT passing in a calendar object to the getDate and getTimestamp methods. In my scenario, the JDBC driver just doesn’t implement these versions of the methods and only supports calling the non-Calendar method. Something like the enable\_utc\_calendar option shown below. source: name: “DATE” enable\_utc\_calendar: false dremio: name: “date” source: name: “TIMESTAMP” enable\_utc\_calendar: false dremio: name: “timestamp”

---

_[View the full topic](https://community.dremio.com/t/arp-is-so-restrictive-i-dont-even-want-to-use-it-anymore/5070)._