When i built kylin_sales_cube in Apache Kylin,i get the error:
ERROR [main] org.apache.kylin.engine.mr.KylinReducer:java.lang.NoSuchMethodError: org.apache.hadoop.fs.FileSystem.setStoragePolicy(Lorg/apache/hadoop/fs/Path;Ljava/lang/String;)V
when i built my own cube,i got same error.
please help!
versions: kylin3.1.3 hadoop2.7.3 hbase1.7.1 hive2.3.9
It looks like kylin 3.1 and hadoop 2.7 are not compatible. Maybe try kylin < 2.5 ?
You can find more info about compatibility here:
https://kylin.apache.org/docs31/install/index.html
Related
I am trying to run Corda nodes on macOS El Capitan with JDK 1.8.0_60 by following the instructions here: https://docs.corda.net/getting-set-up.html.
I am getting the following error:
CAPSULE EXCEPTION: Could not parse version: -9.0.1 while processing
system property java.home:
/Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/jre
java.lang.IllegalArgumentException: Could not parse version: -9.0.1
How can I fix this?
Although its older thread, i encountered it today and stumbled upon this page and thought to share my findings.
Actually Oracle changed the numbering style from java9 (like 9.0.1) and it seems you have it installed. You will have to point to jdk 1.8.x so make it work until capsule is updated to work with java9.
Running Corda nodes requires a JDK version greater than JDK 8u121. If you upgrade your JDK, this error will disappear.
pact-jvm-provider-maven_2.11 works with Java8, but not Java7. Getting the following error
[ERROR] Failed to execute goal au.com.dius:pact-jvm-provider-maven_2.11:3.5.0:verify (default-cli) on project product-xapi-service: Execution default-cli of goal au.com.dius:pact-jvm-provider-maven_2.11:3.5.0:verify failed: Unable to load the mojo 'verify' in the plugin 'au.com.dius:pact-jvm-provider-maven_2.11:3.5.0' due to an API incompatibility: org.codehaus.plexus.component.repository.exception.ComponentLookupException: au/com/dius/pact/provider/maven/PactProviderMojo : Unsupported major.minor version 52.0
I don't see the mention of requirement of Java 8 as well. Does it support Java 7 at all?
Actually, i find the documentation specifying the versions here https://github.com/DiUS/pact-jvm. Thanks.
I've been learning Symfony and I used this page as a guide on how to install it.
I installed/fetched various branches:
# symfony new testonly27 2.7
# symfony new testonly28 2.8
# symfony new testonly30 3.0
# symfony new testonlylts lts
On all instances, I tried viewing the welcome page. It only works in 2.7.x.
On 2.8 and LTS, I get this error (different path names of course for 2.8 and LTS):
Parse error: syntax error, unexpected 'class' (T_CLASS), expecting identifier (T_STRING) in /opt/www/testonly28/vendor/doctrine/common/lib/Doctrine/Common/Proxy/ProxyGenerator.php on line 62
On 3.x, I get this error:
Parse error: syntax error, unexpected '{' in /opt/www/testonly30/var/bootstrap.php.cache on line 2094
Any ideas what I could be doing wrong? Thanks a lot :)
You appear to be using PHP <= 5.5.
The relevant line in the Doctrine ProxyGenerator is
'baseProxyInterface' => Proxy::class,
The ::class keyword syntax was added in PHP 5.5.
Symfony 3.0 requires PHP >= 5.5.9.
Symfony 2.8 claims to require PHP 5.3.9, but somehow, the version of Doctrine you've pulled in requires 5.5 as well, so that's why it's not working for you either.
You need to install php >= v5.5 since what it complains about is Proxy::class, which was introduced in 5.5
I have a written a very simple blueprint.yaml to install the MongoDB on a VM. When I am trying to upload the blueprint it gives me below error:
"An error occurred on the server: 400: Invalid blueprint - provider_context CONTEXT not found"
I am using following:
1. Cloudify CLI and Manager version: 3.3
2. It is successfully validated but issue comes while uploading blueprint.
3. I am using the embedded Nodecellar application blueprint
Any kind of help is appreciated.
Thanks,
Sanjiv
In most cases you will receive this error because you have a very large file in the same directory of the blueprint.
Please look for large files and move them from the blueprint directory or sub-directory's
Best,
Jonathan
This is fixed. Issue was with the manager bootstrap process.
I'm using Cloudify 2.7 with OpenStack Icehouse.
I have deployed with success a tomcat service.
In the Cloudify log, I see:
WARNING [org.cloudifysource.usm.tail.RollingFileReader] - In RollingFileReader: file not found
Can someone help me to understand the meaning of the error?
Thanks.
The Cloudify RollingFileReader is explained here:
https://github.com/CloudifySource/cloudify/blob/master/USM/src/main/java/org/cloudifysource/usm/tail/RollingFileReader.java
In this case, it means that Cloudify was expecting a log file to be created, but none was found. This is probably not a critical error.
Note that Cloudify 2 has reached End-of-Life. You should consider moving to Cloudify 3