datanucleus-api-jdo | DataNucleus persistence using the JDO API | Object-Relational Mapping library

It's quite possible it needs to be updated in the VM. It's included in the VM purely as a convenience - as it's not an officially supported or included part of CDH it doesn't go through all the same testing as everything else.

The root cause of the failure is this:

Please refer to this article where was described how to run spark on windows 10 with hadoop support. Spark on windows

I'm one of the main dev of TiSpark. Sorry for your bad experience with it.

Due to my docker problem, I cannot directly reproduce your issue but it seems you hit one of the bug fixed recently. https://github.com/pingcap/tispark/pull/862/files

1. The tutorial document is not quite up-to-date and points to an older version. That's why it didn't work with spark 2.1.1 as in tutorial. We will update it ASAP.
2. Newer version of TiSpark doesn't use tidbMapDatabase anymore but hooks with catalog directly instead. Method tidbMapDatabase remains for backward compatibility. Unfortunately, the tidbMapDatabase had a bug（when we ported it from older version） that it retrieves timestamp for query only once you call the function. That causes TiSpark always uses old timestamp to do snapshot reading and newer data would never be seen by it.

In newer version of TiSpark (TiSpark 2.0+ with Spark 2.3+), databases and tables are directly hooked into catalog services and you can directly call

You can use properties instead of persistence.xml Actually, I have done a similar example using properties. Another issue is maybe you are missing some dependencies, I am sharing pom.xml. try using that you maybe get the results. It is easy to do if you are using Maven. You also need to do enhance for that as displaying in official docs.

http://www.datanucleus.org/products/accessplatform/jdo/getting_started.html

For that, you need to follow

http://www.datanucleus.org/products/accessplatform_3_2/jdo/enhancer.html

POM.xml

After a long search, I found that the reason the application could not load the class org.apache.spark.deploy.yarn.ApplicationMaster is because this isn't the version of ApplicationMaster the EMR core instance uses - it uses org.apache.hadoop.yarn.applications.distributedshell.ApplicationMaster, which requires the CLASSPATH segment in the input to include /usr/lib/hadoop-yarn/*. I changed the two parameters in the input XML of the REST request and it succeeded to launch. I'll still need to configure the correct CLASSPATH for the EMR implementation to get the application to complete successfully, but the main challenge of this question is solved.

Update: eventually I decided that adding a step to the EMR and using the arguments there is actually a much easier way to handle it. I added to the maven dependencies the EMR AWS Java SDK:

At the very end of this migration page, there is a section labeled "Issues with JPA/JDO Datanucleus enhancement," which links to a StackOverflow example with a working gradle configuration for Datanucleus. I would look very closely for any differences between this canonical example and your own gradle build file.

i tried the merge strategy as per sbt documentation , i think it is still leaving some duplicate sources error so find from other stakoverflow questions to discard every duplicate meta-inf as per below strategy.

Since I can't reproduce the issue copy-pasting just your example code into a new file, I bet that in your real code String is actually shadowed by something else. To verify this theory you can try to change you signature to