Hi Ratish,
Thank you very much for raising this issue/discussion. I wonder: In JDBC
it's only possible to get the auto-incremented value for a single column.
That was also the inspiration for the way the metamodel API was designed I
think. So that leads me to think - is it even meaningful for this
Github user q977734161 commented on the issue:
https://github.com/apache/metamodel/pull/205
I try to make an empty commit to trigger rebuild:
`git commit --allow-empty -m "Empty commit to trigger rebuild"`
It seems build successfully.
---
Better late than never ... I finally got around to publish the release on
dist.apache.org and update the website!
Cheers and congratulations on another good Apache MetaModel version!
Den tir. 11. dec. 2018 kl. 21.57 skrev Kasper Sørensen <
i.am.kasper.soren...@gmail.com>:
> Hi all,
>
> I'm glad
Github user kaspersorensen commented on the issue:
https://github.com/apache/metamodel/pull/205
Hmm. I overspoke - I cannot do that. @q977734161 you'll probably have to
make an empty commit to trigger rebuild:
```
git commit --allow-empty -m "Empty commit to trigger rebuil
Github user kaspersorensen commented on the issue:
https://github.com/apache/metamodel/pull/205
I'll have Travis rebuild it to see what happens ...
---
Github user LosD commented on the issue:
https://github.com/apache/metamodel/pull/205
Error might be unrelated. All runs are good, except on OracleJDK8, where an
Excel test fails inside Apache POI.
It could easily be the Excel context that has issues. We recently changed
it,
GitHub user kaspersorensen opened a pull request:
https://github.com/apache/metamodel/pull/206
Update hive-jdbc to version 2.3.4, addressing CVE-2018-1314
See https://nvd.nist.gov/vuln/detail/CVE-2018-1314 for details on the
vulnerability in the previous versions.
You can merge thi
