[jira] [Resolved] (ASTERIXDB-2216) Intermittent Failure in RSSRecordReaderTest
[
https://issues.apache.org/jira/browse/ASTERIXDB-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Maxon resolved ASTERIXDB-2216.
--
Resolution: Fixed
> Intermittent Failure in RSSRecordReaderTest
> ---
>
> Key: ASTERIXDB-2216
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2216
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: EXT - External data
>Reporter: Murtadha Makki Al Hubail
>Assignee: Michael Blow
>Priority: Major
> Labels: triaged
>
> Stacktrace:
> {code:java}
> java.lang.AssertionError: expected:<0> but was:<10>
> at
> org.apache.asterix.external.input.record.reader.RSSRecordReaderTest.fetchFromLoremWebsite(RSSRecordReaderTest.java:62)
> {code}
> Standard Error:
> 05:49:15.268 [main] INFO
> org.apache.asterix.external.input.record.reader.rss.RSSRecordReader -
> EVENT: Feed Polled. URL = http://lorem-rss.herokuapp.com/feed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ASTERIXDB-2132) Replace ITracer.check
[ https://issues.apache.org/jira/browse/ASTERIXDB-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Maxon resolved ASTERIXDB-2132. -- Resolution: Fixed > Replace ITracer.check > - > > Key: ASTERIXDB-2132 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-2132 > Project: Apache AsterixDB > Issue Type: Bug >Reporter: Abdullah Alamoudi >Assignee: Till Westmann >Priority: Major > > ITracer.check call replace the tracer with a no op tracer if tracing is not > enabled. > However, it is creating some confusion is to how to use the tracer. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ASTERIXDB-2190) Fix support for the timeout parameter
[
https://issues.apache.org/jira/browse/ASTERIXDB-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Maxon resolved ASTERIXDB-2190.
--
Resolution: Fixed
> Fix support for the timeout parameter
> -
>
> Key: ASTERIXDB-2190
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2190
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: API - HTTP API
>Reporter: Till Westmann
>Assignee: Till Westmann
>Priority: Major
> Labels: triaged
>
> There are 3 issues regarding the use of the {{timeout}} parameter for the
> {{query/service}} API:
> # the parameter is not supported for urlencoded requests
> # the result status should be {{timeout}} if the request times out and not
> {{failure}}
> # invalid values for the {{timeout}} parameter are not handled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ASTERIXDB-1711) Clean up class names
[ https://issues.apache.org/jira/browse/ASTERIXDB-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Maxon resolved ASTERIXDB-1711. -- Resolution: Fixed > Clean up class names > > > Key: ASTERIXDB-1711 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-1711 > Project: Apache AsterixDB > Issue Type: Task > Components: *DB - AsterixDB, HYR - Hyracks >Reporter: Till Westmann >Assignee: Till Westmann >Priority: Major > > Some classes have names that include "AQL" (even though they are not language > specific) or "Asterix" (even tough that's part of package names). > We should aim to name classes based on their functionality and clean up class > names that are not named that way. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ASTERIXDB-1711) Clean up class names
[ https://issues.apache.org/jira/browse/ASTERIXDB-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325400#comment-17325400 ] Ian Maxon commented on ASTERIXDB-1711: -- im gonna assume this is done by now- feel free to reopen if not > Clean up class names > > > Key: ASTERIXDB-1711 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-1711 > Project: Apache AsterixDB > Issue Type: Task > Components: *DB - AsterixDB, HYR - Hyracks >Reporter: Till Westmann >Assignee: Till Westmann >Priority: Major > > Some classes have names that include "AQL" (even though they are not language > specific) or "Asterix" (even tough that's part of package names). > We should aim to name classes based on their functionality and clean up class > names that are not named that way. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ASTERIXDB-2884) Nested UDF calls with constant argument NPEs
Ian Maxon created ASTERIXDB-2884:
Summary: Nested UDF calls with constant argument NPEs
Key: ASTERIXDB-2884
URL: https://issues.apache.org/jira/browse/ASTERIXDB-2884
Project: Apache AsterixDB
Issue Type: Bug
Components: FUN - Functions
Affects Versions: 0.9.7
Reporter: Luke Ren
Assignee: Ian Maxon
Fix For: 0.9.7
If you have a Python UDF with a body like:
{code:python}
def echo(a):
return a
{code}
And then define and subsequently call it as a SQL++ UDF nested within itself
with a constant argument like so:
{code:sql}
SELECT echo(echo(5))
{code}
A NPE is thrown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ASTERIXDB-2883) SELECT udf(null); hangs forever in optimization
[ https://issues.apache.org/jira/browse/ASTERIXDB-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Maxon updated ASTERIXDB-2883: - Reporter: Luke Ren (was: Ian Maxon) > SELECT udf(null); hangs forever in optimization > --- > > Key: ASTERIXDB-2883 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-2883 > Project: Apache AsterixDB > Issue Type: Bug > Components: FUN - Functions, SQL - Translator SQL++ >Affects Versions: 0.9.7 >Reporter: Luke Ren >Priority: Minor > > Running an external UDF with a constant null argument seems to get stuck > forever in optimization. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ASTERIXDB-2883) SELECT udf(null); hangs forever in optimization
Ian Maxon created ASTERIXDB-2883: Summary: SELECT udf(null); hangs forever in optimization Key: ASTERIXDB-2883 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2883 Project: Apache AsterixDB Issue Type: Bug Components: FUN - Functions, SQL - Translator SQL++ Affects Versions: 0.9.7 Reporter: Ian Maxon Running an external UDF with a constant null argument seems to get stuck forever in optimization. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ASTERIXDB-2793) SQL++ grammar page is missing
[ https://issues.apache.org/jira/browse/ASTERIXDB-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Maxon reassigned ASTERIXDB-2793: Assignee: Ian Maxon Resolution: Fixed seems to work now > SQL++ grammar page is missing > - > > Key: ASTERIXDB-2793 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-2793 > Project: Apache AsterixDB > Issue Type: Bug > Components: DOC - Documentation >Reporter: Wail Y. Alkowaileet >Assignee: Ian Maxon >Priority: Minor > > The SQL++ grammar page gives 404. > [https://ci.apache.org/projects/asterixdb/SQLPP.html|https://ci.apache.org/projects/asterixdb/SQLPP.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
