Oracle Fusion Middleware Known Issues in Oracle Stream Analytics

Transcription

1 Oracle Fusion Middleware Known s in Oracle Stream Analytics E June 2018

2 Oracle Fusion Middleware Known s in Oracle Stream Analytics, E Copyright 2018, Oracle and/or its affiliates. All rights reserved. Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agencyspecific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

3 Contents Preface Audience Documentation Accessibility Conventions Related Documents iv iv iv v 1 Known s Unexpected Message While Adding a Filter to Join Stage 1-1 Batch Delay Increases When HA is Enabled 1-2 Same user cannot login multiple times 1-2 Target stage does not get updated if previous stage is edited 1-2 Values of Drop-down List not seen when the Live Output Table has a single row 1-2 Metadata Export of Dashboards is not supported 1-3 Metadata Export of Custom Stages is not supported 1-3 Metadata Export of Cubes is not supported 1-3 Metadata Export of Scoring Stages is not supported 1-4 Metadata Export of Predictive Models is not supported 1-4 Metadata Export of Visualizations is not supported 1-4 Improper Connection Pooling Size in Jetty 1-4 No Data Seen in Live Output Table when the Pipeline is Published 1-5 SDO_GEOMETRY Not Supported in Coherence Cache 1-6 Pattern Cannot Detect Events Correctly 1-6 Pipeline is Stuck with "Listening for Events" Message 1-6 Default Character Limit for Text Fields 1-7 Limited Support for Predictive Models 1-7 iii

4 Preface Preface This document lists the known issues and limitations in Oracle Stream Analytics. Topics: Audience Audience Documentation Accessibility Conventions Related Documents This document is intended for all users of Oracle Stream Analytics. Documentation Accessibility Conventions For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at ctx=acc&id=docacc. Accessible Access to Oracle Support Oracle customers who have purchased support have access to electronic support through My Oracle Support. For information, visit lookup?ctx=acc&id=info or visit ctx=acc&id=trs if you are hearing impaired. The following text conventions are used in this document: Convention boldface italic monospace Meaning Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. iv

5 Preface Related Documents Documentation for Oracle Stream Analytics is available on Oracle Help Center. Also see the following documents for reference: Understanding Oracle Stream Analytics Quick Installer for Oracle Stream Analytics Developing Custom Jars and Custom Stages in Oracle Stream Analytics Spark Extensibility for CQL in Oracle Stream Analytics Using Oracle Stream Analytics v

6 1 Known s The limitations and known issues in Oracle Stream Analytics are listed in this document. Topics: Unexpected Message While Adding a Filter to Join Stage Batch Delay Increases When HA is Enabled Same user cannot login multiple times Target stage does not get updated if previous stage is edited Values of Drop-down List not seen when the Live Output Table has a single row Metadata Export of Dashboards is not supported Metadata Export of Custom Stages is not supported Metadata Export of Cubes is not supported Metadata Export of Scoring Stages is not supported Metadata Export of Predictive Models is not supported Metadata Export of Visualizations is not supported Improper Connection Pooling Size in Jetty No Data Seen in Live Output Table when the Pipeline is Published SDO_GEOMETRY Not Supported in Coherence Cache Pattern Cannot Detect Events Correctly Pipeline is Stuck with "Listening for Events" Message Default Character Limit for Text Fields Limited Support for Predictive Models Unexpected Message While Adding a Filter to Join Stage Bug Number: A Pipeline is broken. Please fix all invalid stages. message appears when you try to add a filter in a join stage. This is a known issue. 1-1

7 Chapter 1 Batch Delay Increases When HA is Enabled Batch Delay Increases When HA is Enabled Bug Number: While publishing a pipeline, if you enable HA you can see that the batch scheduling is delayed. This is a known issue. Same user cannot login multiple times Bug Number: Multiple logins from different browser instances using the same user id is not supported in Oracle Stream Analytics. Even though you are not working on the same artifacts, logging in to the application using the same user credentials from multiple places is not allowed. Target stage does not get updated if previous stage is edited Bug Number: When any of the previous stages are updated, the changes are not propagated to the target stage. The live output table in the target stage does not show any events. This is a known issue. Re-configure the target by selecting No Target in the target configuration section. Values of Drop-down List not seen when the Live Output Table has a single row Bug Number:

8 Chapter 1 Metadata Export of Dashboards is not supported Full values within the drop-down list are not seen when the live output table has a single row. This is a known issue. Pull the horizontal splitter up so that more of the table is visible. Metadata Export of Dashboards is not supported Bug Number: The metadata export functionality for dashboards is not supported in this release of Oracle Stream Analytics. This is a limitation. Metadata Export of Custom Stages is not supported Bug Number: The metadata export functionality for pipelines that contain custom stages is not supported in this release of Oracle Stream Analytics. Metadata Export of Cubes is not supported Bug Number: The metadata export functionality of a cube is not supported in this release of Oracle Stream Analytics. 1-3

9 Chapter 1 Metadata Export of Scoring Stages is not supported Metadata Export of Scoring Stages is not supported Bug Number: The metadata export functionality for pipelines that contain scoring stages is not supported in this release of Oracle Stream Analytics. Metadata Export of Predictive Models is not supported The metadata export functionality of predictive models is not supported in this release of Oracle Stream Analytics. This is a limitation. Metadata Export of Visualizations is not supported The metadata export functionality for visualizations is not supported in this release of Oracle Stream Analytics. This is a limitation. Improper Connection Pooling Size in Jetty Bug Number: Jetty slows down because of an improper connection pooling size. You must allocate more size for pooling if not explicitly specified. 1-4

10 Chapter 1 No Data Seen in Live Output Table when the Pipeline is Published Add the connection pool size in the configuration. The sample JDBC configuration looks like the following: <New id="osads" class="org.eclipse.jetty.plus.jndi.resource"> <Arg> <Ref refid="wac"/> </Arg> <Arg>jdbc/OSADataSource</Arg> <Arg> <New class="oracle.jdbc.pool.oracledatasource"> <Set name="url">jdbc:oracle:thin:@myhost.example.com:1521:osadb</set> <Set name="user">{osa_user}</set> <Set name="password">{osa_user_pwd}</set> <Set name="connectioncachingenabled">true</set> <Set name="connectioncacheproperties"> <New class="java.util.properties"> <Call name="setproperty"><arg>minlimit</arg><arg>1</arg></call> <Call name="setproperty"><arg>maxlimit</arg><arg>15</arg></call> <Call name="setproperty"><arg>initiallimit</arg><arg>1</arg></ Call> </New> </Set> </New> </Arg> </New> Example 1-1 Example Title No Data Seen in Live Output Table when the Pipeline is Published Bug Number: Sometimes no data is seen in the target stage of the live output when you publish the pipeline. Exit the pipeline editor and come back to the pipeline. 1-5

11 Chapter 1 SDO_GEOMETRY Not Supported in Coherence Cache SDO_GEOMETRY Not Supported in Coherence Cache Bug Number: In coherence cache, data type conversion to SDO_GEOMETRY is not supported. This is a limitation. Pattern Cannot Detect Events Correctly Bug Number: When you have configured the batch duration as 1 second for underlying Spark Streaming, the pattern match clause cannot detect events sequence correctly happening within an interval of less than or equal to 1 second. This is a limitation. Pipeline is Stuck with "Listening for Events" Message Bug Number: When you create a file stream with Read whole content option enabled, the pipeline is stuck at the message Listening for Events and no data appears in the live output table. Turn off the Read whole content option to see the events streaming in the live output table. 1-6

12 Chapter 1 Default Character Limit for Text Fields Default Character Limit for Text Fields Bug Number: There is a limitation on the size of text fields in pipelines: events with text fields exceeding 1024 characters will not be processed. Limited Support for Predictive Models The menu commands for creating Predictive Models and Scoring Stages are marked Beta, for example, Predictive Model (Beta). The Beta label indicates that the functionality has been tested, but is not fully supported. The import and scoring of Predictive Models might contain undocumented limitations and you should use them as is. 1-7