I'm trying to export data with Raven.smuggler from one RavenDB server of version 1.0
and import it to other RavenDB server of version 2.0
I'm getting file load exception, due to lucene.net version differences.
Is it possible to migrate data from one version of RavenDB to another?
what is the best way to do it?
I've already read the following url:
http://ravendb.net/docs/server/administration/export-import
thanks for you help :-)
EDIT:
"unhandled Exceptions: system.net.webException: Error: System.IO.FileLoadException: could not load file or assembly 'Lucene.Net, Version=2.9.4.1.....' or one of its dependencies.
The located assembly's manifest definition does not match the assembly reference..."
In the older version of Raven i was using Lucene Analyzer 2.9, which not exists in the new version. I'm guessing that's the problem.
You can absolutely move data between versions using smuggler.
Please post the full error you are seeing. Including stack trace.
Related
Refer the raised jira issue in below link .
https://wso2.org/jira/browse/IDENTITY-4633
Any solutions for solving this issue..,
We tried to temperorly solve this issue by editing sqlscripts.java file by downloading it from github, compiled it and tried to pack in same jar file (using winzip, as jar files are zip finally).
As part of the change we had removed TOKEN_SCOPE column from relevant sql query, but still error in log describes 'invalid column TOKEN_SCOPE'
Kindly suggest to make any further changes or share me the jar file.
I am using wso2 identity server v5.1.0
Thanks.
This issue seems to be already reported in https://wso2.org/jira/browse/IDENTITY-4532
This issue is already fixed in 5.2.0 which will be released soon. You can try the 5.2.0 beta from https://github.com/wso2/product-is/releases/tag/v5.2.0-beta
You can find the fix from the PR in the jira I have pointed.
I'm using talend open studio to push salesforce data to my redshift database. By pushing data using the following:
1. tSalesforceInput
2. tMap
3. tFileOutputDelimited
4. tRedshiftOutput
I am only getting about 2-5 rows/s which does not work at all for me.
By pushing the delimited file to tS3Put and then pushing data to redshift the transfer would go MUCH faster, about 500 rows/s. The issue I continue to face is that I get the error:
AWS authentication requires a valid Date or x-amz-date header (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: CC9C86CCC65625C0
And I have no idea how to solve. I have tried using tLibraryLoad to load joda time 2.8.2 before running and then running after but it still fails. Any advice greatly appreciated.
I also had this problem using Talend 6.1 The issue is an incompatibility of Java8, the AWS SDK and the joda-time 2.3 library that Talend bundles.
The solution I found was adapted from: TalendForge
Download joda-time 2.8.2 jar from Joda Time
Add a tLibraryLoad and point it to the new joda-time jar file you downloaded.
Go to your project's Run tab/Advanced Settings and add an additional JVM argument of:
-Xbootclasspath/p:$ROOT_PATH/../lib/joda-time-2.8.2.jar
I did an upgrade from Typo3 4.5 LTE to 6.2 LTE, following the instructions found here: stack overflow
Now during the process of using the Upgrade wizard the Excepiton #1314516809 occured.
Then I went to the db using my php-myadmin and corrected the CaseSensitive-Value as recommended here:wiki.typo3
but the error stays. Rereading the code i realized, that the files, which could not be found, had doubled file extensions like
File /_migrated/RTE/RTEimage.jpeg.jpeg does not exist.
How can I get rid of them?
Maybe this will help.
Migration of RTE images
You must modify the database table sys_file_storage and remove the image entries which cause problems. The images of the migration folder should not remain here.
Validation framework which has been rolled up as part of the JEE6 spec (WL12). Both the WL10 and WL12 versions of our application were deployed with the following open source libraries:
JSR-303 / validation-api.jar (version 1.0)
Hibernate Validator (version 4.2.0)
However, the libraries are also bundled with WL 12 (modules directory). Note that the Hibernate Validator version is slightly different.
modules.javax.validation_1.0.0.jar
hibernate.validator_4.1.0.jar
With our WL12 run we are getting below exception:
javax.validation.ValidationException: Unable to get available provider
Attempted Solutions
Our next attempt was to use the WebLogic FilteringClassLoader to prefer the libraries from our application (APP-INF/lib directory) by specifying them in the weblogic-application.xml file (i.e. choose our versions over WebLogic’s). We were already doing this for several other open source libraries in WL10:
<prefer-application-packages>
<package-name>com.google.common.*</package-name>
<package-name>org.apache.commons.lang.*</package-name>
<package-name>org.apache.commons.logging.*</package-name>
<package-name>org.apache.commons.beanutils.*</package-name>
<package-name>org.apache.commons.collections.*</package-name>
<package-name>antlr.*</package-name>
<package-name>javax.validation.*</package-name>
<package-name>org.hibernate.validator.*</package-name>
</prefer-application-packages>
After making that change, our application experienced the following run-time error trying to process any request that makes use of the validation framework:
javax.validation.ValidationException: Unable to get available provider resolvers.
at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:259)
at web20.hibernate.validation.ValidatorFactoryConfigurator.getValidatorFactory(ValidatorFactoryConfigurator.java:39)
at web20.hibernate.validation.ValidationHandlerImpl.handleHibernateValidations(ValidationHandlerImpl.java:180)
at web20.hibernate.validation.ValidationHandlerImpl.performValidation(ValidationHandlerImpl.java:255)
at web20.hibernate.validation.ValidationHandlerImpl.validateAndFormatMessages(ValidationHandlerImpl.java:302)
at web20.hibernate.validation.ValidationHandlerImpl.validateUsingHibernateGroups(ValidationHandlerImpl.java:113)
at service.serviceapp.performValidations(serviceapp.java:392)
at service.serviceapp.performValidations(serviceapp.java:379)
at service.TransactionalServiceImpl.search(TransactionalServiceImpl.java:300)
Given that Bean Validation is part of the EE standard, I assume there is some code Bean Validation integration code which causes the problem. I see two potential solutions:
Patch the WL instance and upgrade to the Validator version you want to use
Try writing your own ValidationProvider. Internally it could just delegate to the Hibernate Validator classes. If you then add a validation.xml to your application, specifying your custom provider, WL should bootstrap this one. TBH, I don't know whether this will work. There are many unknowns and I don't know enough about the integration of WL and Bean Validation.
Personally, I think I would just try to upgrade the Validator version used in WL.
I'm trying to modify a .net application and I'm new to this. First step is attempting to deobfuscate the code using reflexil and I get the following error:
Reflexil is unable to clean this assembly: Member 'System.RuntimeTypeHandle "bunch of obfustatcated jibberish"(System.Int32)' is declared in another module and needs to be imported
The application comes with a bunch of dll's that it certainly uses, so I assume the declaration is in one of those files. How do I import this module?
In case it's helpful, reflexil says it was obfuscated with .NET Reactor 4.1
I decided to try de4not to deobfuscate and it worked without this issue.