Hitachi Vantara Pentaho Community Forums
Results 1 to 16 of 16

Thread: Testing goals for the week of 6/18

  1. #1
    dmoran Guest

    Arrow Testing goals for the week of 6/18

    This is the first official week of community testing. We will concentrate on metadata and the metadata editor. Please report any issues or comments by replying to this thread. Include the platform, operating system, database, browser and any other configuration information that may be important.

    For this phase of testing we assume that you are a knowledgeable Pentaho user and are comfortable with downloading and installing the platform and components. This is not meant to be a test script but an outline to get you started using metadata and begin to get feedback on the documentation and user experience.

    Refer to the FAQ and 1.6 Testing Home page for questions and resources.


    • Download and install the Milestone 4 platform: Milestone 4 version 1.5.4
    • Start the platform (refer to the Getting Started with the BI Platform guide)
    • Use your browser and try the samples to verify you are configured correctly (Default URL is http://localhost:8080/pentaho)
    • Verify that web based query and reporting is working by selecting "New Report" from the "Go" menu item. Drag and drop a few items and press the "Go" button at the bottom to preview.
    • If you were successful - great! Otherwise verify the above steps and if all else fails, reply to this post for help.
    • Now the fun part, download the Pentaho Metadata Editor - PME M4 1.5.4
    • Install the Pentaho Metadata Editor by following the documentation. Chapter 02 has the installation instructions.
    • Follow the documentation to build metadata on top of your own data and publish to the platform.
    • Give your feedback
    • Test your current solutions, actions, reports, etc. to make sure that they still work as expected in this new release.
    Last edited by dmoran; 06-19-2007 at 12:43 PM.

  2. #2
    rbpetersen Guest

    Default WAQR Issues

    1. The WAQR causes out of memory errors when returning large resultsets. We have to fix this. It seems the SQL Action Sequence allows for specifying the type of resultset to avoid memory issues. Is there anyway to do this for WAQR?

    2. We want to customize the WAQR wizard. First we need a new format; Pipe delimited instead of comma delimited. We could hopefully define the type of resultset to be used for this format as well (see above)

    3. After we save the WAQR as an Action Sequence it cannot be opened in the design studio (JFreeReort Specification Error). This looks like a bug. Hopefully we can use the Action Sequence generated from the WAQR in other Action Sequences. Also, this may be the place to tweak the output format or type of resultset used.

  3. #3
    dmoran Guest

    Default

    I'm looking into these issues.

    Thanks,
    Doug

  4. #4

    Default Permissions

    I try to use the permissions function but it doesn't work. (with 1.5.2 it works)

  5. #5
    dmoran Guest

    Default

    Thanks,

    This is documentated in JIRA case BISERVER-29

  6. #6
    Join Date
    Jun 2005
    Posts
    115

    Default

    Item 1 above was assigned a JIRA case of BISERVER-36: WAQR wasn't generating a <live>true</live> tag in the generated xaction. Since this is a report xaction this should always be the case. It has been resolved in the current code line and should fix the memory problems.

    Bill

  7. #7
    Join Date
    Jun 2005
    Posts
    115

    Default

    Item 3 above is documented in JIRA case PLATFORM-1025

  8. #8
    Join Date
    Jun 2005
    Posts
    115

    Default

    Reference to Item 2 above. In the context of the Pentaho BI Platform, how would you use the pipe delimited file? Would some kind of post processing help?

    thanks,

    Bill

  9. #9

    Unhappy Unhappy Pentaho-demo without Internet connection

    Sys:
    - Micro$oft Windows XP Family Edition SP2
    - Dual-Core 1.83GHz, Go RAM

    pentaho_demo-1.5.4.716-0 :
    Do : Unzip + launch
    Spec : behind a proxy or without an internet connection

    BUG 1 : Launch WSLD
    Note : anoying for a "demo" version
    Level : 1 anoying
    Description : Can't deploy the wsdl pachage
    LOG :
    see join file

    BUG 2 : WAQ&R
    Note : without a internet connection -> seems to be the problem
    Level : 4 severe
    Description :
    Logged as Joe
    On sample data I choose
    BC_CUSTOMERS_COUNTRY - Group Level 1
    BC_CUSTOMERS_CUSTOMERNUMBER -> detail -> center
    BC_CUSTOMERS_PHONE -> detail
    BC_ORDER_DETAILS_PRICEEACH -> detail -> formating "$ 1,234; ($ 1,234)
    Add Constraint : BC_ORDER_DETAILS_PRICEEACH > 0
    I obtain nothing in the browser. The plateform is wainting something... I do CTRL+C kill the current thread and it comes back
    Note that some of my client doesn't have access to Internet on their server
    LOG :
    see join file

    BUG 3 : Reporting Samples
    Note : Warning of usage which will not be supported in the future
    Level : 1 annoying
    Description :
    For Xaction:
    custom-parameter-page-example2.xaction
    JFree_ChartComponent.xaction
    JFree_XQuery_Chart_report.xaction
    JFree_XQuery_report.xaction
    custom-parameter-page-example.xaction
    LOG :
    see join file

    BUG 4 : Reporting Samples
    Note : -
    Level : 4 severe
    Description : I launch MDX_report.xaction and MDX_report_XLS.xaction in the same time, MDX_report_XLS.xaction crashed. If I redo it it works
    OUPUT:
    see join file
    LOG :
    see join file

    Request 1 : Feature request on samples for demo version
    Note :
    Priority (1 high, 5 low) : 5 low
    Description : On dynamically_show_columns.xaction the based select must return a not-empty report. So the user will try and show a report. Without having to change the selection.

    BUG 5: JFreeChart error
    Note :
    Level : 3
    Description :
    Logged as Joe
    Launch Sales_by_Customer.xaction as a web-page : http://localhost:8080/pentaho/ViewAc...wheels/reports
    It didn't shows the bar chart
    LOG :
    Nothing useful

    BUG 6 : JfreeChart Error 2
    Note :
    Level : 3
    Description :
    idem than Bug 5 with http://localhost:8080/pentaho//ViewA...6-01&type=html
    Attached Files Attached Files
    Cedric CLAIDIERE
    Aprolis
    www.aprolis.com

  10. #10
    Join Date
    Jun 2005
    Posts
    115

    Default

    BUG 1: See PLATFORM-1033

    BUG 2: See JIRA case BISERVER-38

    BUG 3: See JIRA case BISERVER-47

    BUG 4: Unable to reproduce in current build

    BUG 5 & 6: See JIRA case BISERVER-48

    REQUEST 1: See JIRA case BISERVER-49

    Bill

  11. #11

    Default Problem with Hello mail samole demo

    Quote Originally Posted by dmoran View Post
    This is the first official week of community testing. We will concentrate on metadata and the metadata editor. Please report any issues or comments by replying to this thread. Include the platform, operating system, database, browser and any other configuration information that may be important.

    For this phase of testing we assume that you are a knowledgeable Pentaho user and are comfortable with downloading and installing the platform and components. This is not meant to be a test script but an outline to get you started using metadata and begin to get feedback on the documentation and user experience.

    Refer to the FAQ and 1.6 Testing Home page for questions and resources.

    • Download and install the Milestone 4 platform: Milestone 4 version 1.5.4
    • Start the platform (refer to the Getting Started with the BI Platform guide)
    • Use your browser and try the samples to verify you are configured correctly (Default URL is http://localhost:8080/pentaho)
    • Verify that web based query and reporting is working by selecting "New Report" from the "Go" menu item. Drag and drop a few items and press the "Go" button at the bottom to preview.
    • If you were successful - great! Otherwise verify the above steps and if all else fails, reply to this post for help.
    • Now the fun part, download the Pentaho Metadata Editor - PME M4 1.5.4
    • Install the Pentaho Metadata Editor by following the documentation. Chapter 02 has the installation instructions.
    • Follow the documentation to build metadata on top of your own data and publish to the platform.
    • Give your feedback
    • Test your current solutions, actions, reports, etc. to make sure that they still work as expected in this new release.
    Hi,
    i'm using the last milestone of pentaho demo version 1.5.4 and i have problems to send emails (the sample example). i did exctly the same in the file as shown in the file email_config_gmail.xml to configure my gmail parametters(i copied and pasted email_config_gmail.xml in email_config.xml and i added my user@gmail.com and my password) but nothing works and i don't know if it is a bug i read many discussions on the forum peaple always say that maybe it is a bug when they upgraded to the version 1.2 and they say the mail works well for the old version 1.0. i don't know exactly if it is a bug or i'm doing something wrong and i need help please.
    the error message which i have is the following:
    FailedError: Email.ERROR_0011 - SMTP send failed: [hammamr@hotmail.com] - javax.mail.SendFailedException: Sending failed; nested exception is: class javax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 587; nested exception is: java.net.ConnectException: Connection timed out: connect (org.pentaho.plugin.email.EmailComponent)Debug: Starting execute of samples/getting-started/HelloEmail.xaction (org.pentaho.core.solution.SolutionEngine)
    Debug: Getting runtime context and data (org.pentaho.core.solution.SolutionEngine)
    Debug: Loading action sequence definition file (org.pentaho.core.solution.SolutionEngine)
    Debug: SolutionRepository.DEBUG_FILE_PATH - getFile path=D:\pentaho\pentaho-demo\pentaho-solutions\samples\getting-started\HelloEmail.xaction (org.pentaho.repository.filebased.solution.SolutionRepository)
    Debug: Adding variable source request to parameter to (org.pentaho.repository.filebased.solution.SolutionRepository)
    Debug: Adding default value of "" to parameter to (org.pentaho.repository.filebased.solution.SolutionRepository)
    Debug: Adding variable source request to parameter subject (org.pentaho.repository.filebased.solution.SolutionRepository)
    Debug: Adding default value of "Hello World" to parameter subject (org.pentaho.repository.filebased.solution.SolutionRepository)
    Debug: audit: instanceId=95e680fb-258d-11dc-ba49-4972f9895280, objectId=org.pentaho.core.runtime.RuntimeContext, messageType=action_sequence_start (org.pentaho.core.runtime.RuntimeContext)
    Debug: validateComponent validating component EmailComponent (org.pentaho.core.runtime.RuntimeContext)
    Debug: Validating component for action HelloEmail.xaction (org.pentaho.plugin.email.EmailComponent)
    Debug: Executing action sequence (org.pentaho.core.runtime.RuntimeContext)
    Debug: Executing action definition: Iteration 0 (org.pentaho.core.runtime.RuntimeContext)
    Debug: audit: instanceId=95e680fb-258d-11dc-ba49-4972f9895280, objectId=EmailComponent, messageType=component_execution_started (org.pentaho.core.runtime.RuntimeContext)
    Debug: execute pre-audit (org.pentaho.core.runtime.RuntimeContext)
    Debug: Setting component log level to DEBUG (org.pentaho.core.runtime.RuntimeContext)
    Debug: Initializing component (org.pentaho.core.runtime.RuntimeContext)
    Debug: executeComponent starting audited execute (org.pentaho.core.runtime.RuntimeContext)
    Debug: execute validation=true (org.pentaho.plugin.email.EmailComponent)
    Debug: Execute to=[hammamr@hotmail.com], from=hammamr@gmail.com (org.pentaho.plugin.email.EmailComponent)
    Debug: Execute cc=[], bcc=[] (org.pentaho.plugin.email.EmailComponent)
    Debug: Execute subjectHello World (org.pentaho.plugin.email.EmailComponent)
    Debug: Execute messagePlainGreetings from the Pentaho BI Platform email component! (org.pentaho.plugin.email.EmailComponent)
    Debug: Execute messageHtmlnull (org.pentaho.plugin.email.EmailComponent)
    Error: Email.ERROR_0011 - SMTP send failed: [hammamr@hotmail.com] - javax.mail.SendFailedException: Sending failed; nested exception is: class javax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 587; nested exception is: java.net.ConnectException: Connection timed out: connect (org.pentaho.plugin.email.EmailComponent)
    Debug: executeComponent finished audited execute (org.pentaho.core.runtime.RuntimeContext)
    Error: RuntimeContext.ERROR_0012 - ActionDefinition for EmailComponent did not execute successfully (org.pentaho.core.runtime.RuntimeContext)
    Debug: audit: instanceId=95e680fb-258d-11dc-ba49-4972f9895280, objectId=org.pentaho.core.runtime.RuntimeContext, messageType=action_sequence_failed (org.pentaho.core.runtime.RuntimeContext)
    Error: SolutionEngine.ERROR_0007 - Action sequence execution failed (org.pentaho.core.solution.SolutionEngine)

    Server Version 1.2.0 build 534 GA

    Please help
    Thanks in advance!!

  12. #12

    Default Bug on xaction with combo box

    Hello,

    my friend found a bug in xaction when it have a combo box, if the data that will populate the combo box comes from database and the select statement returns only one datum, combo box don't populate, to test it, put a limit 1 on the select statement or put a where clause that will return only one datum and you can see what I'm talking about.

    Sorry for my poor english.

    Thanks

  13. #13
    Join Date
    Apr 2007
    Posts
    78

    Default

    In response to the "Problem with Hello mail samole demo", please see the following message:
    http://forums.pentaho.org/showthread...d=1#post163576

  14. #14

    Default Metadata Editor and AS400

    Hello,

    I worked on DB2/AS400 and the PMD didn't seems to works with librairies, so when I greate my Businness view, it create SQL request like "SELECT * FROM ARTI;" which throw an error.
    The correct SQL is : "SELECT * FROM DIVERS.ARTI;"

    Thanks

    Cedric
    Cedric CLAIDIERE
    Aprolis
    www.aprolis.com

  15. #15
    dmoran Guest

    Default

    Thanks,

    Logged in JIRA as bug.

    http://jira.pentaho.org/browse/PMD-138

  16. #16
    wgorman Guest

    Default

    Hi Cedric,

    Our DB2 Expert here pointed me to the JDBC property "currentSchema" which should solve your problem.

    For your example, add ":currentSchema=DIVERS;" to the end of your JDBC driver connection string.

    Here is a link to documentation on various jdbc properties:
    http://publib.boulder.ibm.com/infoce...d/rjvdsprp.htm

    Hope that helps!

    Will

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.