[
https://issues.apache.org/jira/browse/JENA-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497188#comment-13497188
]
Fergal Monaghan edited comment on JENA-241 at 8/20/13 2:48 PM:
---------------------------------------------------------------
Hi all, apologies but there will be a delay in contributing this until SAP has
put in place appropriate user support resources and opened HANA's JDBC driver
to public use. A few months back when I originally posted this I filled in the
right paperwork and made a few calls to start the ball rolling, but obviously
HANA is proprietary technology and SAP is very careful about exposing
APIs/integration before having proper support and customer care resources for
the same in place. Since this would be considered a back end API/integration,
they have asked me to hold back on submitting this until such a time as when
this support will be in place. I am monitoring the situation but I do not have
a timescale for when or if I would be allowed to submit this, and I can't
really comment further. In fairness, I can see the company's point of view:
somewhere there is an IT support guy who would suddenly be bombarded with user
support requests for a component he has never heard of and never agreed to
support. This was brought home to me today when I received my first request for
further assistance by email based on this Jira issue (thanks for the email, I
will respond pointing back to this comment). I wish this could be faster or
that I could be more help.
was (Author: fergalmonaghan):
Hi all, apologies but I am held up indefinetely it seems by Legal. A few
months back when I originally posted this I filled in the right paperwork and
made a few calls to start the ball rolling, but obviously HANA is proprietary
technology and they are very careful about exposing APIs/integration before
having proper support and customer care resources for the same in place. Since
this would be considered a back end API/integration, they have restrained me
from submitting this until such a time as when this support will be in place. I
am monitoring the situation but I do not have a timescale for when or if I
would be allowed to submit this, and I can't really comment further. In
fairness, I can see Legal's point as I received my first request for further
assistance by email today based on this Jira issue (thanks for the email, I
will respond pointing back to this comment!). I wish this could be faster or
that I could be more help.
> Add support for SAP database
> ----------------------------
>
> Key: JENA-241
> URL: https://issues.apache.org/jira/browse/JENA-241
> Project: Apache Jena
> Issue Type: Improvement
> Components: SDB
> Affects Versions: SDB 1.3.5
> Reporter: Fergal Monaghan
> Assignee: Rob Vesse
> Attachments: JENA-SDB-HANA-applied.patch, JENA-SDB-HANA.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> I would like to contribute my complete and tested patch to make SDB
> compatible with SAP's new in-memory, column-store (-possible) database
> codenamed HANA. I followed the instructions here [1] to the letter, created
> the patch and tested by applying it cleanly. Now I can run SPARQL endpoints
> on top of SAP's DB, and I'd like everyone else to be able to do this too. I
> just need to check with SAP legal before I attach the patch to this issue as
> described at [1]. Keep up the good work guys!
> [1] http://incubator.apache.org/jena/getting_involved/index.html
--
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
