[ASTERIXDB-1366] Unable to create Twitter feed adaptor

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Component/s: EXT - External data, ING - Ingestion
• Assignee: Abdullah Alamoudi
• Reporter: Xikui Wang
• Created: 23/Mar/16 23:32
• Updated: 08/Mar/18 04:27
• Resolved: 06/Apr/16 07:02

Description

I met this exception when connect data feed to dataset:
AQL:

use dataverse feeds;
connect feed TwitterFeed to dataset Tweets;

Exception Info:

org.apache.hyracks.algebricks.common.exceptions.AlgebricksException: unable to create adapter
at org.apache.asterix.metadata.feeds.FeedMetadataUtil.getPrimaryFeedFactoryAndOutput(FeedMetadataUtil.java:557)
at org.apache.asterix.metadata.declared.AqlMetadataProvider.buildFeedIntakeRuntime(AqlMetadataProvider.java:617)
at org.apache.asterix.app.external.FeedOperations.buildFeedIntakeJobSpec(FeedOperations.java:83)
at org.apache.asterix.aql.translator.QueryTranslator.handleConnectFeedStatement(QueryTranslator.java:2203)
at org.apache.asterix.aql.translator.QueryTranslator.compileAndExecute(QueryTranslator.java:368)
at org.apache.asterix.aql.translator.QueryTranslator.compileAndExecute(QueryTranslator.java:254)
at org.apache.asterix.api.http.servlet.APIServlet.doPost(APIServlet.java:148)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:546)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:483)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:228)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:956)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:411)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:188)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:891)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:114)
at org.eclipse.jetty.server.Server.handle(Server.java:353)
at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:598)
at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1076)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:805)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:218)
at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:427)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:510)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.access$000(SelectChannelEndPoint.java:34)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:40)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:450)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.asterix.common.exceptions.AsterixException: The parameter parser must be specified.
at org.apache.asterix.external.util.ExternalDataUtils.validateParameters(ExternalDataUtils.java:89)
at org.apache.asterix.external.provider.AdapterFactoryProvider.getAdapterFactory(AdapterFactoryProvider.java:44)
at org.apache.asterix.metadata.feeds.FeedMetadataUtil.getPrimaryFeedFactoryAndOutput(FeedMetadataUtil.java:513)
... 28 more

The reason might be that the configuration passed into AdapterFactoryProvider has a null parser..