Hi Nirdesha, +1 to use "data source" since it doesn't represent a connection to a database. It merely lists down the places where a chart can read data from.
Thanks, Dunith On Mon, Jul 20, 2015 at 12:11 PM, Nirdesha Munasinghe <[email protected]> wrote: > Hi Dunith, > > If it's a source of data, then it is best renamed as data source (two > words). A datasource means a connection to a database. +1 for help tips in > the UI. > > Cheers, > -Nirdesha > > On Sat, Jul 18, 2015 at 7:15 PM, Praneesha Chandrasiri <[email protected] > > wrote: > >> We can put a note in the doc to mention that we need to have a source of >> data as a prerequisite for the gadget generation wizard, and link it to the >> page where content on creating streams is documented. >> >> On Mon, Jul 13, 2015 at 8:33 AM, Dunith Dhanushka <[email protected]> >> wrote: >> >>> Hi Manoj, >>> >>> What we meant by the term 'datasource' is any object that provides data >>> for the visualization gadget. According to the dashboard context there are >>> two datasources types, DAL tables and event streams. >>> I agree with that the wording 'datasource' is already associated with >>> Carbon datasources and quite misleading in the dashboard's context. >>> Probably we can rename it to something else and add some context sensitive >>> help text to guide users. >>> >>> Thanks, >>> Dunith >>> >>> On Sat, Jul 11, 2015 at 2:46 AM, Gimantha Bandara <[email protected]> >>> wrote: >>> >>>> [Adding Dunith] >>>> >>>> On Sat, Jul 11, 2015 at 2:44 AM, Manoj Kumara <[email protected]> wrote: >>>> >>>>> Hi Gimantha, >>>>> >>>>> Previously I thought its related to the datasouces we are define >>>>> instead of the streams we create. Anyway I think the 'datasource' term is >>>>> bit misleading WDYT ? >>>>> >>>>> Thanks for the support. >>>>> >>>>> Regards, >>>>> Manoj >>>>> >>>>> >>>>> *Manoj Kumara |* Senior Software Engineer >>>>> Inc. *| **lean. enterprise. middleware.* >>>>> #20, Palm Grove, Colombo 03, Sri Lanka >>>>> *Mobile:* +94 713 448188 *|** Work:* +94 112 145345 >>>>> >>>>> >>>>> On Fri, Jul 10, 2015 at 3:25 PM, Gimantha Bandara <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi Manoj, >>>>>> >>>>>> Can you check if you can see the tables through message console in >>>>>> management console under Interactive Analytics? >>>>>> >>>>>> On Sat, Jul 11, 2015 at 1:43 AM, Manoj Kumara <[email protected]> wrote: >>>>>> >>>>>>> Hi Gokul, >>>>>>> >>>>>>> I tried create a gadget but it dose not show the available >>>>>>> datasouces. Reported a issue [2]. >>>>>>> >>>>>>> [1] >>>>>>> https://docs.wso2.com/display/DAS300/Adding+Gadgets+to+a+Layout#AddingGadgetstoaLayout-Selectingadatasource >>>>>>> [2] https://wso2.org/jira/browse/BAM-2094 >>>>>>> >>>>>>> Regards, >>>>>>> Manoj >>>>>>> >>>>>>> >>>>>>> *Manoj Kumara |* Senior Software Engineer >>>>>>> Inc. *| **lean. enterprise. middleware.* >>>>>>> #20, Palm Grove, Colombo 03, Sri Lanka >>>>>>> *Mobile:* +94 713 448188 *|** Work:* +94 112 145345 >>>>>>> >>>>>>> >>>>>>> On Wed, Jul 8, 2015 at 10:10 AM, Gokul Balakrishnan <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>> The WSO2 DAS team is pleased to announce the beta release of WSO2 >>>>>>>> DAS 3.0.0. The distribution is available for download here >>>>>>>> <https://svn.wso2.org/repos/wso2/people/inosh/wso2das-3.0.0-BETA.zip> >>>>>>>> . >>>>>>>> >>>>>>>> The release includes the following bug fixes, improvements, and >>>>>>>> tasks: >>>>>>>> >>>>>>>> Bug Fixes >>>>>>>> >>>>>>>> - [BAM-1962 <https://wso2.org/jira/browse/BAM-1962>] - License >>>>>>>> issue in org.wso2.carbon.analytics.message.tracer.handler.feature >>>>>>>> - [BAM-2033 <https://wso2.org/jira/browse/BAM-2033>] - Graceful >>>>>>>> Shutdown and Graceful Restart not working >>>>>>>> - [BAM-2034 <https://wso2.org/jira/browse/BAM-2034>] - WSO2 DAS >>>>>>>> doesnt work properly when started with an offset >>>>>>>> - [BAM-2035 <https://wso2.org/jira/browse/BAM-2035>] - Event >>>>>>>> Stream simulator doesn't work and throwing >>>>>>>> java.lang.ClassCastException in >>>>>>>> console >>>>>>>> - [BAM-2036 <https://wso2.org/jira/browse/BAM-2036>] - Date and >>>>>>>> other fields are showing as null in application and system logs >>>>>>>> - [BAM-2037 <https://wso2.org/jira/browse/BAM-2037>] - Cannot >>>>>>>> login to the Dashboard when server start with offset >>>>>>>> - [BAM-2038 <https://wso2.org/jira/browse/BAM-2038>] - Table >>>>>>>> Name, By Date Range, By Query fields are getting moved when select >>>>>>>> the By >>>>>>>> Facet values >>>>>>>> - [BAM-2043 <https://wso2.org/jira/browse/BAM-2043>] - Need to >>>>>>>> change the deployment directory folder structure >>>>>>>> - [BAM-2045 <https://wso2.org/jira/browse/BAM-2045>] - NPE when >>>>>>>> starting Gadget generation wizard >>>>>>>> - [BAM-2046 <https://wso2.org/jira/browse/BAM-2046>] - Persist >>>>>>>> attribute ticks are not retain in the UI >>>>>>>> - [BAM-2047 <https://wso2.org/jira/browse/BAM-2047>] - Unused >>>>>>>> folders inside dep/server folder >>>>>>>> - [BAM-2050 <https://wso2.org/jira/browse/BAM-2050>] - Unable >>>>>>>> to start two DAS instances in the same machine with offset >>>>>>>> - [BAM-2053 <https://wso2.org/jira/browse/BAM-2053>] - [UI] >>>>>>>> Data purging lands browser on blank page >>>>>>>> - [BAM-2054 <https://wso2.org/jira/browse/BAM-2054>] - Purging >>>>>>>> Data Failed with OutOfMemoryError >>>>>>>> - [BAM-2055 <https://wso2.org/jira/browse/BAM-2055>] - >>>>>>>> [Intermittent] Purging fails with BatchUpdateException on MySQL >>>>>>>> - [BAM-2056 <https://wso2.org/jira/browse/BAM-2056>] - [UI] >>>>>>>> Adding JMX Server profile fails >>>>>>>> - [BAM-2057 <https://wso2.org/jira/browse/BAM-2057>] - Cannot >>>>>>>> update the Analytic Script information, when added a wrong cron job >>>>>>>> value >>>>>>>> - [BAM-2058 <https://wso2.org/jira/browse/BAM-2058>] - Spark >>>>>>>> script was not deployed when included in CAR >>>>>>>> - [BAM-2060 <https://wso2.org/jira/browse/BAM-2060>] - Cannot >>>>>>>> retrieve table data by giving 'from' 'to' time-stamp >>>>>>>> - [BAM-2065 <https://wso2.org/jira/browse/BAM-2065>] - Event >>>>>>>> Tracer does not work properly >>>>>>>> - [BAM-2068 <https://wso2.org/jira/browse/BAM-2068>] - New >>>>>>>> Dashboard pages get duplicate content as the first page >>>>>>>> - [BAM-2071 <https://wso2.org/jira/browse/BAM-2071>] - Include >>>>>>>> 'Complex Event Processor' Server Role >>>>>>>> - [BAM-2076 <https://wso2.org/jira/browse/BAM-2076>] - Error >>>>>>>> when using the analytics API in remote mode with HTTPS protocol. >>>>>>>> - [BAM-2078 <https://wso2.org/jira/browse/BAM-2078>] - Remove >>>>>>>> streaming events from spark feaure to different bundle from >>>>>>>> spark.core. >>>>>>>> - [BAM-2080 <https://wso2.org/jira/browse/BAM-2080>] - Back up >>>>>>>> tool does not back up data batch wise >>>>>>>> - [BAM-2084 <https://wso2.org/jira/browse/BAM-2084>] - >>>>>>>> Introduce syncing/flushing for the HDFS Analytics file system >>>>>>>> >>>>>>>> Improvements >>>>>>>> >>>>>>>> - [BAM-2022 <https://wso2.org/jira/browse/BAM-2022>] - Enable >>>>>>>> custom UDFs for DAS >>>>>>>> - [BAM-2028 <https://wso2.org/jira/browse/BAM-2028>] - Tune the >>>>>>>> Spark configurations in DAS for best performance >>>>>>>> - [BAM-2029 <https://wso2.org/jira/browse/BAM-2029>] - >>>>>>>> Implement multiple data sources in DAS >>>>>>>> - [BAM-2030 <https://wso2.org/jira/browse/BAM-2030>] - >>>>>>>> Implement custom analyzer support in spark using registry lookup >>>>>>>> - [BAM-2048 <https://wso2.org/jira/browse/BAM-2048>] - Add >>>>>>>> secure vault support to analytics API configuration >>>>>>>> - [BAM-2074 <https://wso2.org/jira/browse/BAM-2074>] - Event >>>>>>>> sink to store only one event when Realtime (CEP) within DAS is >>>>>>>> configured >>>>>>>> in HA mode >>>>>>>> - [BAM-2075 <https://wso2.org/jira/browse/BAM-2075>] - Make >>>>>>>> event sink related parameters configurable with configuration file, >>>>>>>> and >>>>>>>> have a worker pool to store the events received. >>>>>>>> - [BAM-2077 <https://wso2.org/jira/browse/BAM-2077>] - >>>>>>>> Introducing AUTO mode in carbon analytics API to switch between >>>>>>>> LOCAL and >>>>>>>> REMOTE automatically. >>>>>>>> - [BAM-2079 <https://wso2.org/jira/browse/BAM-2079>] - Search a >>>>>>>> field by its whole content to match the exact content >>>>>>>> - [BAM-2082 <https://wso2.org/jira/browse/BAM-2082>] - Multiple >>>>>>>> Record Store Support >>>>>>>> - [BAM-2083 <https://wso2.org/jira/browse/BAM-2083>] - Refactor >>>>>>>> HBase Analytics Datastore to remove obsolete operations >>>>>>>> - [BAM-2085 <https://wso2.org/jira/browse/BAM-2085>] - Add CEP >>>>>>>> Execution Manager feature to DAS pack >>>>>>>> >>>>>>>> Tasks >>>>>>>> >>>>>>>> - [BAM-2064 <https://wso2.org/jira/browse/BAM-2064>] - Rename >>>>>>>> analytics-dataservice-config.xml to analytics-config.xml >>>>>>>> - [BAM-2073 <https://wso2.org/jira/browse/BAM-2073>] - Add >>>>>>>> disable/enable to analytics components in DAS >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> The documentation for this release can be found at the WSO2 DAS >>>>>>>> 3.0.0 Documentation >>>>>>>> <https://docs.wso2.com/display/DAS300/WSO2+Data+Analytics+Server+Documentation> >>>>>>>> site. >>>>>>>> >>>>>>>> We value your feedback and suggestions are welcome, and issues >>>>>>>> could be reported at the WSO2 DAS Issue Tracking >>>>>>>> <https://wso2.org/jira/browse/BAM> page. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> WSO2 DAS Development Team. >>>>>>>> >>>>>>>> [*] Download: >>>>>>>> https://svn.wso2.org/repos/wso2/people/inosh/wso2das-3.0.0-BETA.zip >>>>>>>> >>>>>>>> [*] Documentation: >>>>>>>> https://docs.wso2.com/display/DAS300/WSO2+Data+Analytics+Server+Documentation >>>>>>>> >>>>>>>> [*] Issue reporting: https://wso2.org/jira/browse/BAM >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Gokul Balakrishnan >>>>>>>> Senior Software Engineer, >>>>>>>> WSO2, Inc. http://wso2.com >>>>>>>> Mob: +94 77 593 5789 | +1 650 272 9927 >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Gokul Balakrishnan >>>>>>>> Senior Software Engineer, >>>>>>>> WSO2, Inc. http://wso2.com >>>>>>>> Mob: +94 77 593 5789 | +1 650 272 9927 >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Architecture mailing list >>>>>>>> [email protected] >>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Dev mailing list >>>>>>> [email protected] >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Gimantha Bandara >>>>>> Software Engineer >>>>>> WSO2. Inc : http://wso2.com >>>>>> Mobile : +94714961919 >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Gimantha Bandara >>>> Software Engineer >>>> WSO2. Inc : http://wso2.com >>>> Mobile : +94714961919 >>>> >>> >>> >>> >>> -- >>> Regards, >>> >>> Dunith Dhanushka, >>> Senior Software Engineer - BAM, >>> WSO2 Inc, >>> >>> Mobile - +94 71 8615744 >>> Blog - dunithd.wordpress.com <http://blog.dunith.com> >>> Twitter - @dunithd <http://twitter.com/dunithd> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Thanks & Best Regards, >> *Praneesha Chandrasiri* >> *Technical Writer* >> *WSO2 Inc. * >> *Mobile: +(94) 718156888 <%2B%2894%29%20718156888>* >> *E-mail: [email protected] <[email protected]>* >> >> -- >> You received this message because you are subscribed to the Google Groups >> "WSO2 Documentation" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/a/wso2.com/d/optout. >> > > > > -- > > Thanks, > > Nirdesha Munasinghe, > WSO2 Inc. > Web:http://wso2.com > > Mobile: +94 776321920 > -- Regards, Dunith Dhanushka, Senior Software Engineer WSO2 Inc, Mobile - +94 71 8615744 Blog - dunithd.wordpress.com <http://blog.dunith.com> Twitter - @dunithd <http://twitter.com/dunithd>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
