Hi,
We have come across many cases where DAS tables stored in the EVENT or
PROCESSED stores (which have encoded names to comply with DB vendor
limitations) cannot be identified as representing which actual table just
by looking at them. This is a very useful functionality to have, especially
when
Hi Gokul,
This is a much-needed functionality. Can we have this for APIM Analytics
2.1.0 as well?
On Thu, Jan 11, 2018 at 11:01 AM, Gokul Balakrishnan wrote:
> Hi,
>
> We have come across many cases where DAS tables stored in the EVENT or
> PROCESSED stores (which have encoded names to comply w
Hi Fazlan,
Yes, the plan is to port this functionality to the latest product Analytics
distributions as well as to DAS 3.1.0.
Thanks,
On 11 January 2018 at 11:07, Fazlan Nazeem wrote:
> Hi Gokul,
>
> This is a much-needed functionality. Can we have this for APIM Analytics
> 2.1.0 as well?
>
>
Hi Gokul,
+1 to have a feature which returns the actual table name from the encoded
table name that exists in the data storage.
But IMHO, having REST API for this is not a correct way of doing, because
REST APIs are intended to integrate this with external systems, and hence
core analytics data o
Hi Sinthuja,
Agree with your point. However, a new script will come with its own
complexities such as segregating permissions and preventing users from
retrieving names of tables not belonging to their tenant. In addition, we
already have a REST API operation for doing it the other way
(human-read
Hi Gokul,
On Thu, Jan 11, 2018 at 11:41 AM, Gokul Balakrishnan wrote:
> Hi Sinthuja,
>
> Agree with your point. However, a new script will come with its own
> complexities such as segregating permissions and preventing users from
> retrieving names of tables not belonging to their tenant.
>
Any
Have to agree with Sinthuja on this.
IMO this is a simple utility function. People will be mostly using this
while debugging an issue to get the actual table name. Having script makes
things much easy and simple IMO.
Thanks
*,Sajith Ravindra*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
le
Hi all,
Was this implemented? if so can someone point me to the documentation? I
need to find the actual table name using the encoded name. If there is any
other alternative please let me know.
On Thu, Jan 11, 2018 at 8:21 AM, Sajith Ravindra wrote:
> Have to agree with Sinthuja on this.
>
> IM
Hi Fazlan,
It is there in apim analytics 2.2.0 and also as a WUM update in 2.1.0
On Fri, Apr 20, 2018 at 5:19 AM, Fazlan Nazeem wrote:
> Hi all,
>
> Was this implemented? if so can someone point me to the documentation? I
> need to find the actual table name using the encoded name. If there is
+[Rukshani]
Hi All,
We need to update the documentation [1] by adding the following entry for
the $subject implementation.
GET (with auth) https://:9443/analytics/tables/
/actualName
[1] - https://docs.wso2.com/display/DAS320/Analytics+REST+API+Guide
Regards,
SajithD
On Fri, Apr 20, 2018 at 1
Hi Sajith,
I will do this within the week. Thank you for sharing this information.
Best Regards,
Rukshani.
On Fri, Apr 20, 2018 at 11:59 AM, Sajith Perera wrote:
> +[Rukshani]
>
> Hi All,
>
> We need to update the documentation [1] by adding the following entry for
> the $subject implementatio
Hi Rukshani,
Please find the requested information:
Sample cURL command
curl -H "Content-Type: application/json" -H "Authorization: Basic
YWRtaW46YWRtaW4=" -v
https://localhost:9443/analytics/tables/ANX___7LtvlqNk_/actualName -k
Example
GET (with auth) https://
:9443/analytics/tables/ANX___7Ltvl
Hello Sajith,
Thank you for this information. Now the documentation is updated
accordingly. Can you please check [1]?
[1]
https://docs.wso2.com/display/DAS320/Inferring+the+Actual+Table+Name+from+the+Encoded+Name
Best Regards,
Rukshani.
On Tue, Apr 24, 2018 at 3:42 PM, Sajith Perera wrote:
>
Hi Rukshani,
Reviewed!, Looks good.
Regards,
SajithD
On Tue, May 1, 2018 at 1:49 PM, Rukshani Weerasinha
wrote:
> Hello Sajith,
>
> Thank you for this information. Now the documentation is updated
> accordingly. Can you please check [1]?
>
> [1] https://docs.wso2.com/display/DAS320/Inferring+t
14 matches
Mail list logo