Re: Weekly status

[Till Westmann]

Did you mean to send this to asterixresea...@ics.uci.edu?

Cheers,
Till

On 27 Oct 2017, at 9:24, abdullah alamoudi wrote:


Hi Everyone,
I will not be able to attend this week's meeting. Here is my status:

1. Make Active job resume attempt on the same suspend/resume thread
This prevents Metadata locking issue explained in the commit 
message.
2. Set Default dataverse in MetadataProvider and prevents null values 
inside AMutableString.
This prevents NPE during compilation in certain contexts. See 
commit message again.
3. More performance tests. specifically testing the behavior of 
flushes/merges of prefix merge policy

3. Reviewed changes:
- BloomFilter check change.
- Refactor Waiting For Dataset IO Ops
- Feed pipeline refactoring for SQL++


That is about it,
Abdullah.

Weekly status

[abdullah alamoudi]

Hi Everyone,
I will not be able to attend this week's meeting. Here is my status:

1. Make Active job resume attempt on the same suspend/resume thread
This prevents Metadata locking issue explained in the commit message.
2. Set Default dataverse in MetadataProvider and prevents null values inside 
AMutableString.
This prevents NPE during compilation in certain contexts. See commit 
message again.
3. More performance tests. specifically testing the behavior of flushes/merges 
of prefix merge policy
3. Reviewed changes:
- BloomFilter check change.
- Refactor Waiting For Dataset IO Ops
- Feed pipeline refactoring for SQL++


That is about it,
Abdullah.

Re: Status update for GSoC 2017 on GeoAsterixDB [ASTERIXDB-1371]

[Mike Carey]

Nice!!


On 7/3/17 7:56 PM, Riyafa Abdul Hameed wrote:

Dear all,

After familiarizing myself with AQL and SQLPP I have defined a new datatype
which is 'geometry' and have implemented the parse_geojson() which would
take as input a record (object) and return a 'geometry'. I have also
implemented a printer for the 'geometry' datatype.
Further I have implemented a function st_area() that would take as input a
'geometry' and return the area of the given geometry.
I have been using the Esri geometry api[1] for implementing these so far.
Because of the limitations of this api, following Geometry types in GeoJSON
are currently supported:

- Point
- MultiPoint
- Polygon
- MultiPolygon
- LineString
- MultiLineString
- GeometryCollection (printer support is currently not available)

The changes have been submitted to gerrit[2]

[1] https://github.com/Esri/geometry-api-java
[2] https://asterix-gerrit.ics.uci.edu/1838

Thank you.
Yours sincerely,
Riyafa

Status update for GSoC 2017 on GeoAsterixDB [ASTERIXDB-1371]

[Riyafa Abdul Hameed]

Dear all,

After familiarizing myself with AQL and SQLPP I have defined a new datatype
which is 'geometry' and have implemented the parse_geojson() which would
take as input a record (object) and return a 'geometry'. I have also
implemented a printer for the 'geometry' datatype.
Further I have implemented a function st_area() that would take as input a
'geometry' and return the area of the given geometry.
I have been using the Esri geometry api[1] for implementing these so far.
Because of the limitations of this api, following Geometry types in GeoJSON
are currently supported:

   - Point
   - MultiPoint
   - Polygon
   - MultiPolygon
   - LineString
   - MultiLineString
   - GeometryCollection (printer support is currently not available)

The changes have been submitted to gerrit[2]

[1] https://github.com/Esri/geometry-api-java
[2] https://asterix-gerrit.ics.uci.edu/1838

Thank you.
Yours sincerely,
Riyafa

Re: What is the new path to check Hyracks jobs status in AsterixDB?

[Mike Carey]

JSON:  What's not to love?  :-)


On 4/7/17 5:27 PM, Jianfeng Jia wrote:

That’s a good idea. I haven’t think about the browser plugin. Now it looks 
better!


On Apr 7, 2017, at 4:34 PM, Till Westmann  wrote:

Since the endpoints return JSON, using a JSON formatter plugin for the browser 
seems easier.
Otherwise I think that we’ll need to create a page around it (which is clearly 
feasible as well).

On 7 Apr 2017, at 16:21, Mike Carey wrote:


Could we use the same library that Xikui used for JSON (formatted) as a baby 
step?


On 4/7/17 10:04 AM, Jianfeng Jia wrote:

Got it. (do we have any plan to beautify the UI? :-)
Thanks!


On Apr 7, 2017, at 9:46 AM, Yingyi Bu  wrote:

Hi Jianfeng,

 The admin console has been removed but the REST APIs which return JSON
results are still there.

 Let's take the sample cluster as an example.
 To check nodes:
 http://localhost:16001/rest/nodes/
 http://localhost:16001/rest/nodes/red
 http://localhost:16001/rest/nodes/blue

 To check jobs:
 http://localhost:16001/rest/jobs/
 http://localhost:16001/rest/jobs/JID:0/job-run

Best,
Yingyi


On Thu, Apr 6, 2017 at 5:18 PM, Jianfeng Jia  wrote:


Dear Devs,

We used to have a Hyracks adminconsole web page xxx:/adminconsole  (or
on 16001 port if not using managix) which can watch the details of the
recent jobs. By click into each job we can know Activity Cluster Graph/Job
Timeline etc.

It’s very useful to have a overview of the current system workload (e.g.,
how many queries are running, when did they submit, how long it has ran …).
Right now, the same link returns a following error.
page can’t be found

I’m wondering what is the new path to get the same information? Thanks!



Best,

Jianfeng Jia
PhD Candidate of Computer Science
University of California, Irvine

Re: What is the new path to check Hyracks jobs status in AsterixDB?

[Jianfeng Jia]

That’s a good idea. I haven’t think about the browser plugin. Now it looks 
better!

> On Apr 7, 2017, at 4:34 PM, Till Westmann  wrote:
> 
> Since the endpoints return JSON, using a JSON formatter plugin for the 
> browser seems easier.
> Otherwise I think that we’ll need to create a page around it (which is 
> clearly feasible as well).
> 
> On 7 Apr 2017, at 16:21, Mike Carey wrote:
> 
>> Could we use the same library that Xikui used for JSON (formatted) as a baby 
>> step?
>> 
>> 
>> On 4/7/17 10:04 AM, Jianfeng Jia wrote:
>>> Got it. (do we have any plan to beautify the UI? :-)
>>> Thanks!
>>> 
 On Apr 7, 2017, at 9:46 AM, Yingyi Bu  wrote:
 
 Hi Jianfeng,
 
 The admin console has been removed but the REST APIs which return JSON
 results are still there.
 
 Let's take the sample cluster as an example.
 To check nodes:
 http://localhost:16001/rest/nodes/
 http://localhost:16001/rest/nodes/red
 http://localhost:16001/rest/nodes/blue
 
 To check jobs:
 http://localhost:16001/rest/jobs/
 http://localhost:16001/rest/jobs/JID:0/job-run
 
 Best,
 Yingyi
 
 
 On Thu, Apr 6, 2017 at 5:18 PM, Jianfeng Jia  
 wrote:
 
> Dear Devs,
> 
> We used to have a Hyracks adminconsole web page xxx:/adminconsole  (or
> on 16001 port if not using managix) which can watch the details of the
> recent jobs. By click into each job we can know Activity Cluster Graph/Job
> Timeline etc.
> 
> It’s very useful to have a overview of the current system workload (e.g.,
> how many queries are running, when did they submit, how long it has ran 
> …).
> Right now, the same link returns a following error.
> page can’t be found
> 
> I’m wondering what is the new path to get the same information? Thanks!
> 
> 
> 
> Best,
> 
> Jianfeng Jia
> PhD Candidate of Computer Science
> University of California, Irvine
> 
> 

Re: What is the new path to check Hyracks jobs status in AsterixDB?

[Till Westmann]

Since the endpoints return JSON, using a JSON formatter plugin for the 
browser seems easier.
Otherwise I think that we’ll need to create a page around it (which is 
clearly feasible as well).


On 7 Apr 2017, at 16:21, Mike Carey wrote:

Could we use the same library that Xikui used for JSON (formatted) as 
a baby step?



On 4/7/17 10:04 AM, Jianfeng Jia wrote:

Got it. (do we have any plan to beautify the UI? :-)
Thanks!


On Apr 7, 2017, at 9:46 AM, Yingyi Bu  wrote:

Hi Jianfeng,

 The admin console has been removed but the REST APIs which 
return JSON

results are still there.

 Let's take the sample cluster as an example.
 To check nodes:
 http://localhost:16001/rest/nodes/
 http://localhost:16001/rest/nodes/red
 http://localhost:16001/rest/nodes/blue

 To check jobs:
 http://localhost:16001/rest/jobs/
 http://localhost:16001/rest/jobs/JID:0/job-run

Best,
Yingyi


On Thu, Apr 6, 2017 at 5:18 PM, Jianfeng Jia 
 wrote:



Dear Devs,

We used to have a Hyracks adminconsole web page 
xxx:/adminconsole  (or
on 16001 port if not using managix) which can watch the details of 
the
recent jobs. By click into each job we can know Activity Cluster 
Graph/Job

Timeline etc.

It’s very useful to have a overview of the current system 
workload (e.g.,
how many queries are running, when did they submit, how long it has 
ran …).

Right now, the same link returns a following error.
page can’t be found

I’m wondering what is the new path to get the same information? 
Thanks!




Best,

Jianfeng Jia
PhD Candidate of Computer Science
University of California, Irvine

Re: What is the new path to check Hyracks jobs status in AsterixDB?

[Mike Carey]

Could we use the same library that Xikui used for JSON (formatted) as a 
baby step?



On 4/7/17 10:04 AM, Jianfeng Jia wrote:

Got it. (do we have any plan to beautify the UI? :-)
Thanks!


On Apr 7, 2017, at 9:46 AM, Yingyi Bu  wrote:

Hi Jianfeng,

 The admin console has been removed but the REST APIs which return JSON
results are still there.

 Let's take the sample cluster as an example.
 To check nodes:
 http://localhost:16001/rest/nodes/
 http://localhost:16001/rest/nodes/red
 http://localhost:16001/rest/nodes/blue

 To check jobs:
 http://localhost:16001/rest/jobs/
 http://localhost:16001/rest/jobs/JID:0/job-run

Best,
Yingyi


On Thu, Apr 6, 2017 at 5:18 PM, Jianfeng Jia  wrote:


Dear Devs,

We used to have a Hyracks adminconsole web page xxx:/adminconsole  (or
on 16001 port if not using managix) which can watch the details of the
recent jobs. By click into each job we can know Activity Cluster Graph/Job
Timeline etc.

It’s very useful to have a overview of the current system workload (e.g.,
how many queries are running, when did they submit, how long it has ran …).
Right now, the same link returns a following error.
page can’t be found

I’m wondering what is the new path to get the same information? Thanks!



Best,

Jianfeng Jia
PhD Candidate of Computer Science
University of California, Irvine

Re: What is the new path to check Hyracks jobs status in AsterixDB?

[Jianfeng Jia]

Got it. (do we have any plan to beautify the UI? :-)
Thanks!

> On Apr 7, 2017, at 9:46 AM, Yingyi Bu  wrote:
> 
> Hi Jianfeng,
> 
> The admin console has been removed but the REST APIs which return JSON
> results are still there.
> 
> Let's take the sample cluster as an example.
> To check nodes:
> http://localhost:16001/rest/nodes/
> http://localhost:16001/rest/nodes/red
> http://localhost:16001/rest/nodes/blue
> 
> To check jobs:
> http://localhost:16001/rest/jobs/
> http://localhost:16001/rest/jobs/JID:0/job-run
> 
> Best,
> Yingyi
> 
> 
> On Thu, Apr 6, 2017 at 5:18 PM, Jianfeng Jia  wrote:
> 
>> Dear Devs,
>> 
>> We used to have a Hyracks adminconsole web page xxx:/adminconsole  (or
>> on 16001 port if not using managix) which can watch the details of the
>> recent jobs. By click into each job we can know Activity Cluster Graph/Job
>> Timeline etc.
>> 
>> It’s very useful to have a overview of the current system workload (e.g.,
>> how many queries are running, when did they submit, how long it has ran …).
>> Right now, the same link returns a following error.
>> page can’t be found
>> 
>> I’m wondering what is the new path to get the same information? Thanks!
>> 
>> 
>> 
>> Best,
>> 
>> Jianfeng Jia
>> PhD Candidate of Computer Science
>> University of California, Irvine
>> 
>> 

Re: What is the new path to check Hyracks jobs status in AsterixDB?

[Yingyi Bu]

Hi Jianfeng,

 The admin console has been removed but the REST APIs which return JSON
results are still there.

 Let's take the sample cluster as an example.
 To check nodes:
 http://localhost:16001/rest/nodes/
 http://localhost:16001/rest/nodes/red
 http://localhost:16001/rest/nodes/blue

 To check jobs:
 http://localhost:16001/rest/jobs/
 http://localhost:16001/rest/jobs/JID:0/job-run

Best,
Yingyi


On Thu, Apr 6, 2017 at 5:18 PM, Jianfeng Jia  wrote:

> Dear Devs,
>
> We used to have a Hyracks adminconsole web page xxx:/adminconsole  (or
> on 16001 port if not using managix) which can watch the details of the
> recent jobs. By click into each job we can know Activity Cluster Graph/Job
> Timeline etc.
>
> It’s very useful to have a overview of the current system workload (e.g.,
> how many queries are running, when did they submit, how long it has ran …).
> Right now, the same link returns a following error.
> page can’t be found
>
> I’m wondering what is the new path to get the same information? Thanks!
>
>
>
> Best,
>
> Jianfeng Jia
> PhD Candidate of Computer Science
> University of California, Irvine
>
>

What is the new path to check Hyracks jobs status in AsterixDB?

[Jianfeng Jia]

Dear Devs,

We used to have a Hyracks adminconsole web page xxx:/adminconsole  (or on 
16001 port if not using managix) which can watch the details of the recent 
jobs. By click into each job we can know Activity Cluster Graph/Job Timeline 
etc. 

It’s very useful to have a overview of the current system workload (e.g., how 
many queries are running, when did they submit, how long it has ran …). 
Right now, the same link returns a following error.
page can’t be found

I’m wondering what is the new path to get the same information? Thanks!



Best,

Jianfeng Jia
PhD Candidate of Computer Science
University of California, Irvine

Re: Gerrit Status

[Ian Maxon]

Alright, I will take Gerrit down for upgrade pt.2 in a hour or so
unless anyone objects.

On Mon, Jan 30, 2017 at 11:00 AM, Ian Maxon  wrote:
> Hey guys,
> Just as a heads up, I will probably take Gerrit down again sometime tonight
> to retry the upgrade. I'll send an email a few hours before.
>
> On Fri, Jan 27, 2017 at 4:44 PM, Ian Maxon  wrote:
>>
>> Hey guys,
>> You can use Gerrit again for the time being, I had to roll back the
>> upgrade because there's some issues with the OAuth plugin at the
>> moment. I'm going to try an older version but I have to test it first.
>>
>> I'll send another mail when I take Gerrit down again for a few hours
>> to retry the upgrade.
>>
>> - Ian
>
>

Status

[Wail Alkowaileet]

Hi all,

Unfortunately I won't be able to attend this meeting. And here's my status:
- I was mainly working on the Tuple-Level compaction.
- helped MIT folks on exporting and query the data.
- Finally, there is an initial plan to incorporate Cloudberry in one of our
project (It's targeted for a city instead of a nation).

Thanks

Status

[Taewoo Kim]

I will not be able to attend the Weekly meeting. So, I have attached my
status here:

[Paper]
- Conducting a preliminary experiment on similarity search paper (preparing
similar search queries and sending them to a small dataset)

[Individual]
- Addressed Ian's comments on the full-text implementation step 1 branch
- Reviewed Steven's non-pure branch
- Preparing another index-only plan chunks (select and join rule change)
- Fixed ASTERIXDB-1700
  (if we have multiple same type of indexes on the same field, all of
indexes will be used for a select query.
   Only picking one is enough. E.g., 2-gram and 3-gram index on the same
string field)

Status

[Steven Jacobs]

I will be unable to join the meeting tomorrow, so I'm sending my status.
This week I:

Got the three-node BAD nuclear cluster running
Added test cases and addressed Yingyi's comments and Preston's Jira issue
for nonPures.
Refactored BAD as an extension, and am now trying to get the testing
framework to run

Steven

Re: Status

[Murtadha Hubail]

It's been a busy week for me. I just worked a little bit more on 
AqlMetadataProvider refactoring.

-Murtadha

> On Jul 15, 2016, at 2:10 PM, Chris Hillery  wrote:
> 
> - Discussions inside Couchbase regarding perf testing (meeting with perf
> team member later today)
> - Worked with Mike B a bit on improvements to current functional testing
> 
> Ceej
> aka Chris Hillery

Status

[Chris Hillery]

- Discussions inside Couchbase regarding perf testing (meeting with perf
team member later today)
- Worked with Mike B a bit on improvements to current functional testing

Ceej
aka Chris Hillery