Hi All,
I have noticed multiple naming conventions have been followed by Analytics
REST API [1].
/analytics/tables/{tableName}/indexData
/analytics/drillDownScoreCount
/analytics/tables/{tableName}/keyed_records
/analytics/search_count
/analytics/tables/{tableName}/recordcount
/analytics/rangec
On Fri, Apr 22, 2016 at 10:15 AM, Tharik Kanaka wrote:
> Hi All,
>
> I have noticed multiple naming conventions have been followed by Analytics
> REST API [1].
>
> /analytics/tables/{tableName}/indexData
> /analytics/drillDownScoreCount
>
> /analytics/tables/{tableName}/keyed_records
> /analytics
+1 good point Tharik
And in /analytics/tables/{tableName}/recordcount why is recordcount a
resource at
all? Shouldn't it be returned as an attribute of
/analytics/tables/{tableName}
On Fri, Apr 22, 2016 at 12:57 AM, Sagara Gunathunga wrote:
>
>
> On Fri, Apr 22, 2016 at 10:15 AM, Tharik Kanaka
Hi Tharik,
We implemented this API in the last year and at that time REST API
guidelines were not available. We are planing to fix those according to the
REST API guidance in a next major release.
Regards,
Gihan
On Fri, Apr 22, 2016 at 10:15 AM, Tharik Kanaka wrote:
> Hi All,
>
> I have notice
Hi Tharik,
+1, please open a Jira.
--Srinath
On Sat, Apr 23, 2016 at 4:06 PM, Gihan Anuruddha wrote:
> Hi Tharik,
>
> We implemented this API in the last year and at that time REST API
> guidelines were not available. We are planing to fix those according to the
> REST API guidance in a next m
Hi Srinath,
I have created a JIRA [1] for above improvement.
[1] https://wso2.org/jira/browse/DAS-406
Regards,
On Tue, Apr 26, 2016 at 1:26 PM, Srinath Perera wrote:
> Hi Tharik,
>
> +1, please open a Jira.
>
> --Srinath
>
> On Sat, Apr 23, 2016 at 4:06 PM, Gihan Anuruddha wrote:
>
>> Hi Tha
