API Manager Upgrade 1.5 to 1.6 - repository

Is it correct that the DB-scripts in $WSO2_AM_HOME/dbscripts, only contains migration scripts until version 1.5?
Can we assume that WSO2-AM 1.6 db-repository is the same as version 1.5?

You need to upgrade the databases when migrating from APIM 1.5 ->1.6. You can find the migration scripts and the readme file from [1].
Seems,the relevant scripts has not been included to APIM 1.6.0 packs and created [2] to track this.
[1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/apimgt/1.6.0/modules/distribution/resources/migration-1.5.0_to_1.6.0/
[2] https://wso2.org/jira/browse/APIMANAGER-1969
Thanks;
/Lalaji

Related

How to change Hudi table version via Hudi CLI

How do I change the table version via the Hudi CLI?
Steps:
ssh into EMR
kick off the hudi cli /usr/lib/hudi/cli/bin/hudi-cli.sh. Version of the Hudi CLI is 1.
connect to my table connect --path s3://bucket/db/table
In the desc of the table I see that it is version=3, but I want to use Hudi 0.9.0 to write to the table so I would like to set the table to version=2.
org.apache.hudi.exception.HoodieException: Unknown versionCode:3
at org.apache.hudi.common.table.HoodieTableVersion.lambda$versionFromCode$1(HoodieTableVersion.java:54)
at java.util.Optional.orElseThrow(Optional.java:290)
at org.apache.hudi.common.table.HoodieTableVersion.versionFromCode(HoodieTableVersion.java:54)
at org.apache.hudi.common.table.HoodieTableConfig.getTableVersion(HoodieTableConfig.java:246)
Sadly, I'm not aware of any way to use version 0.9.0 to downgrade 3 to 2, due to the error you are getting. There is no way for version 0.9.0 to know how 0.10.0 was writing things differently.
Recently, AWS has 6.6 available for use, but it isn't well documented. I'd recommend switching over to that, because it has hudi version 0.10.0 and can then do that downgrade.
This link should get updated whenever 6.6 gets updated in the docs.
https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-release-app-versions-6.x.html
Side note, if you are using the bootstrap action script provided by AWS to repair the log4j vulnerability, I'd recommend taking the version 6.5 version provided and editing it to be 6.6. There is not a 6.6 script available at this time, but I did that and was not able to detect any vulnerabilities.
This link provides an explanation on the bootstrap action:
https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-log4j-vulnerability.html

Aerospike Version, any other major upgrades before 3.13.x necessary?

Our Enterprise AS cluster is on v 3.7.3, do we need to upgrade to any of the versions before 3.13.x or can we directly upgrade to the major 3.13.x version?
Nope, shouldn't be a problem to upgrade from 3.7 to 3.13.
Note: As an Enterprise user you have access to our 24 hr support team at support.aerospike.com.

Which Phoenix version should I use with HBase in Cloudera 5.5 and Hortonworks 2.4?

Is there a single version of phoenix that is compatible with HBase provided in both Cloudera 5.5 and Hortonworks 2.4?
Hortonworks provides custom fixes and "backports" to their version of Phoenix in their HDP distribution. Cloudera may do the same as well.
I am assuming that you are asking about a client version that is compatible with both server versions.
Are you using the "thin" client jars? Do you find that your application does not work for one distribution or the other (dependent on which version jars you have)? Your application may work for both distributions if you use the non-thin jars.
If you would like to continue using the thin client, you may have to set phoenix.queryserver.serialization to JSON. HDP 2.3.4+ use PROTOBUF by default whereas CDH does not currently support PROTOBUF.
If you are asking about manually installing a version of the Phoenix server that can be installed on both distributions, both use HBase 1.1.x. Any Phoenix version 4.4+ can be used on either distribution. But I recommend using the version that is distributed with the platform.
A Phoenix 4.5.2 package for CDH 5.5.x is available via Cloudera Labs:
http://blog.cloudera.com/blog/2015/11/new-apache-phoenix-4-5-2-package-from-cloudera-labs/
Note however that Cloudera Labs packages are for dev/test only (not supported by Cloudera).

appixia's cartapi for Prestashop 1.6

appixia's cartAPI is best solution I have found on web for webservice.
Git Source
I am Using same API's for Prestashop from last 1 year for 1.5 version.
Now I have upgraded my prestahop version from 1.5 to 1.6 with latest one. After upgrade I have installed same cartAPI module from Git source but it's not working as they mentioned in it's supported version document,
Prestashop 1.5.x - Tested on 1.5.0.17 through 1.5.3.1
Can anybody help me why this is not working?
Is there anyone who can upgrade this API to work with 1.6 version?
Requested to GIT
Now if I have to try for upgrade what type of changes have to make, please
give suggestions.

RUN#cloud with specific JDK version

Is there a way we can specify the JDK version we are running on? Specifically, I have a java app (non webapp) that has an incompatibility with 1.6.0_35 and is erroring out for me on CloudBees. The package recommends 1.6.0_27, is that possible to specify at deployment time?
you can specify the version with -Rjava_version on the command line - however, fine grained versions are not available (as we tend to update those) - it is more just 1.6, 1.7 or 1.8 lineage. I would recommend in that case -Rjava_version=1.7.