FOSElasticaBundle which version of Elasticsearch? - elasticsearch

I've just installed elasticasearch last version. Looks like this bundle doesn't support version 5.0.2? Cause I've got this error
[Symfony\Component\Debug\Exception\FatalThrowableError]
Wrong parameters for Elastica\Exception\ResponseException([string $message [, long $code [, Throwable $previous = NULL]]])
Which version of elasticasearch should I use?
Thanks

In my current project I run https://www.elastic.co/downloads/past-releases/elasticsearch-2-4-2 with "friendsofsymfony/elastica-bundle": "^3.1"

Related

Laravel Schedule:list produces DateTimeZone error

Laravel Version: 8.78.1
PHP Version: 8.0.10
Description
Whilst creating my first scheduled command, trying to list my schedules with
php artisan schedule:list
throws the error:
DateTime::setTimezone(): Argument #1 ($timezone) must be of type DateTimeZone, null given at vendor/laravel/framework/src/Illuminate/Console/Scheduling/ScheduleListCommand.php:43
changing my command to
php artisan schedule:list --timezone=Europe/London
gives:
DateTime::setTimezone(): Argument #1 ($timezone) must be of type DateTimeZone, string given at vendor/laravel/framework/src/Illuminate/Console/Scheduling/ScheduleListCommand.php:43
Steps To Reproduce:
My schedule:
$schedule->command('email:expired-licences')->weekdays()->at('08:00');
My custom command doesn't actually do anything yet.
Eventually I found a solution if I edited ScheduleListCommand.php
changing:
->setTimezone($this->option('timezone', config('app.timezone')))
to
->setTimezone(new DateTimeZone($this->option('timezone', config('app.timezone'))))
but only if I use the --timezone=Europe/London switch (not sure if this is required), if not then the $this->option doesn't seem to be accepting the config('app.timezone') as a default.
Even:
$schedule->command('route:list')->weekdays()->at('08:00');
doesn't work on my system - not sure what's going on.
This was a bug in the laravel\framework\src\Illuminate\Console\Scheduling\ScheduleListCommand.php and was fixed in the v8.79.0 release

ParseError: 102 Invalid parameter for query: pipeline

After upgrading from Parse Server 2.8.4 to 3.1.3 an aggregate query in cloud code does not work anymore.
The query:
const query = new Parse.Query("MyClass");
const pipeline = {
"sort":{"_created_at":-1}
};
const results = await query.aggregate(pipeline);
fails with error:
ParseError: 102 Invalid parameter for query: pipeline
I also tried the pipeline object as array which also fails:
const pipeline = [
{"sort":{"_created_at":-1}}
];
It seems to fail in ClassesRouter.js which does not recognize the pipeline key.
Why is that?
Update: Opened an issue on GitHub because it looks like a bug.
Try updating both Server and SDK to latest versions.
This issue may have happened because you used a newer SDK on an older version of parse or vice verse

org.apache.kylin.job.exception.ExecuteException: java.lang.NoClassDefFoundError: org/apache/hadoop/hive/serde2/typeinfo/TypeInfo

I find similar error on https://issues.apache.org/jira/browse/KYLIN-2511
env:
hadoop-2.7.1
hbase-1.3.2
apache-hive-2.1.1-bin
apache-kylin-1.6.0-hbase1.x-bin
I've tried copy all the hive libs to kylin, but get another ERROR.
org.apache.hadoop.mapred.YarnChild: Error running child : java.lang.NoClassDefFoundError: org/apache/hadoop/hive/serde2/typeinfo/TypeInfo
The missing class should be in hive-exec-.jar; Check and debug the "bin/find-hive-dependency.sh" to see why it wasn't able to locate this jar from your server. You can manually add it to the "hive_exec_path" variable.
BTW, Kylin 1.6 is quite old, try to upgrade to a 2.x version.
Why you just try the method mentioned in https://issues.apache.org/jira/browse/KYLIN-2511. You'd better prepare the env according to the document of v16. It is better for using the latest version of Kylin. It has more feature and fixes some bugs.

Hibernate seems not to resolve alias correctly

since some days I'm facing the following problem:
I am using Hibernate to do the following Restriction on a criteria:
...
criteria.add(Restrictions.sqlRestriction("1=1 CONNECT BY PRIOR {ProcessEntityworkflowProject}.ID = {ProcessEntityworkflowProject}.PARENT_ID"))
Where "ProcessEntityworkflowProject" is the alias which should be resolved by hibernate.
This alias is set in code properly. I also debugged the code and inspected criteria:
There I could see that a subcriteria in subcriterialist of criteria has this correct alias bound to the association path.
But in SQL logs I see that it is not resolved:
... and this_.EXTERNAL_KEY is not null and 1=1 CONNECT BY PRIOR {ProcessEntityworkflowProject}.ID = {ProcessEntityworkflowProject}.PARENT_ID and processent4_.TYPE_ID=? ...
... or is this output correct and it is resolved later internally?
And in tomcat.log I see that there is a NPE:
java.lang.NullPointerException
at oracle.jdbc.driver.T4C8Oall.getNumRows(T4C8Oall.java:876)
at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:831)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1039)
at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:850)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1134)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3339)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3384)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:92)
at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:139)
at org.hibernate.loader.Loader.getResultSet(Loader.java:1669)
at org.hibernate.loader.Loader.doQuery(Loader.java:662)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224)
at org.hibernate.loader.Loader.doList(Loader.java:2145)
at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029)
at org.hibernate.loader.Loader.list(Loader.java:2024)
at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:94)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1533)
at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:295)
I already found out that this NPE is cause because Oracle JDBC driver can not parse the brackets "{" "}". So I guess that the alias was not resolved properly.
Does anyone of you have an idea what could be wrong or how I could investigate deeper?
Some additional info:
I am using Hibernate 3.2.0 (CR1 afaik), tomcat 5.5, ojdbc14.jar.
Running on RHEL 6.4 and Oracle 11g
Many thx in advance if some of you have an idea ;)
Cheers
Sascha

Assigning the return value of new by reference is deprecated

Install "xampp-win32-1.7.3.exe" and put my php project in htdocs folder. this is working on another machine which having PHP version of 5.3 same version is here also but gives me following error
Deprecated: Assigning the return value
of new by reference is deprecated in
C:\xampp\htdocs\businesscaliber\system\codeigniter\Common.php
on line 62 A PHP Error was encountered
Severity: 8192
Message: Function
set_magic_quotes_runtime() is
deprecated
Filename: codeigniter/CodeIgniter.php
Line Number: 45
Make sure you have your codeigniter version updated to the last version.
The cause of deprecation is Old version like PHP 4 which affects the
this->wsdl =& new wsdl($this->wsdlFile,$this->proxyhost,$this->proxyport,$this->proxyusername,$this->proxypassword,$this->timeout,$this->response_timeout);
and
$GLOBALS['_transient']['static']['nusoap_base']->globalDebugLevel = 9;
all you need to do is Comment them find them in the Line numbers and run again. Goodluck!

Resources