WEEK 5: ENTRY 3

Today at my internship, I worked on activating my Big Query Console within the firm’s authentication and authorization and testing out some of the Queries on the data from the Big Query API. Big Query is a Google Cloud Platform, which is public as well. However, unlike how I can create an account to sign in to the Big Query Console, I had to use my company’s email to access the data housed in the Big Query. The Big Query is quite fascinating because it has the description of the data, the schemas and data types all outlined.  In addition, the console and executable run time is pretty fast and simple to use. 


Like many databases and data, my data is in a relational database format. It is basically arranged in a set of rows and columns. This display eases the struggle of writing the query. One of the queries that my manager needed me to write was , “ A query that returns every host(distinct) and the number of system logs that contain a certain body massage.” Having worked with relational databases in my Database class last semester, it was a very similar approach in using the SELECT statements and other functions when writing SQL Queries. However, there were new syntax and commands like the “LIKE” functions. As a result, I had to spend some moments looking at the documentations and experimenting with those new SQL commands that are apt for the Big Query queries. 


At first, I was able to return the host names and the count of each host name with the body as well, but it was thousands of rows because there were duplicates. Why did I see duplicates? Well, it is because I was not including in my query any command to handle the duplicates. Perhaps I should have expected this prior to running my query, but I did not. To resolve this issue, I added the “DISTINCT” command and “GROUP BY” so that the hot names would not be duplicated. Luckily it worked for me. I have learned that most of what I learned in my database class at Berea College were really handy and I definitely needed to just be more confident and recall what I learned. I wish I had the notes I made during that class with me here, but I would not let that deter my progress and success in implementing the queries because most of the information is in the web.

Comments

Post a Comment

Popular posts from this blog

WEEK 4: ENTRY 3

  Today at my internship, I was assigned the issue of troubleshooting why my GET request Golang code is unable to generate the data from my http server. Since it was a combination of k8s deployment and Golang go, it was trickier and harder than I envisioned. The k8s was mainly used to orchestrate the objects that are needed to generate keytab from my pods. After several debugging: comparing and contrast the referred file I used as a source code coupled with looking up the errors on Stack flow (suggested me to delete my deployment and redeployed), I was still unable to fix the issue. Partly was because I did not understand what the error message was pointing at. Thus, I had to consult a member of the k8s team, who figured out that my deployment.yaml file was missing some configurations that needed to generate my key-tab. Simply, I needed the key-tab in order to be able to make the HTTP Get Request get my desired data.   Although the recommended solution from my consultation wor...
Read more

WEEK 6: ENTRY 3

  At my internship today, I continued unmarshalling the Json data I got back from Big Query API. Having tried replicating the data on the Go playground and using the Go unmarshall function yesterday, I did develop a better understanding of the json structure. I used Go’s struct to do the unmarshalling. Unlike the json data I got from my query, the documentation’s json data does not have any schema metadata and so I thought the same approach would not work. Little did I know that the schema data can be ignored when unmarshalling json data and that you can only concentrate on the part of the Json you want to unmarshall. When I consulted my buddy, he hopped on a zoom call with me and we did pair programming. I was the driver while he was the navigator, basically explaining what we were doing because he has more knowledge on Go and Json data manipulation. Working with him gave me more skills and confidence in what I was doing. He helped in not just using the Go struct, but also in tryi...
Read more

WEEK 7: ENTRY 1

  It sometimes feels like we are not good enough when our tries don’t work. Well at my internship today, I worked on resolving the json unmarshalling issue I was stuck with last Friday. After several back-and-forth consultations with my buddy and manager, I finally got a better understanding of how they wanted me to present the data. Basically, the data should be in a simple json array that could be manipulated easier. This is because as the json comes in key:pair format, I would need to extract all the keys and use those keys to send an HTTPS request to Elasticsearch Rest API.  Even though the approach was well defined and clear to me, I still struggled to implement it using the Golang Struct and Maps. One of the obstacles I had was because after unmarshalling the json data, the output was in a Golang interface type, which was not iterable like say a slice. A Golang slice is the equivalent  of a python array. Therefore, to overcome that barrier, I created an empty slice ...
Read more